Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

CAS-003 > 4.1 Secure enterprise architecture > Flashcards

4.1 Secure enterprise architecture Flashcards

1
Q

Adapt data flow security to meet changing business needs

A
  • enterprises must adapt to the needs of the enterprise

- must start with strong security foundations to allow for easier and faster updates

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

(Standards)

A

mandatory requirements in support of a policy

- HIPAA, PCI DSS, NIST 800 series

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

(Standards)

Competing standards

A

two or more standards available to us to address the same issues

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

(Standards)

Lack of standards

A

new technologies that lack standards, such as IoT devices and blockchain

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

(Standards)

De facto standards

A

standards that are so widely accepted by an industry but have not undertaken formal standardization process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

(Interoperability Issues)

Legacy systems and software/current systems

A

legacy systems are older applications and hardware that are no longer supported by the vendor, but are still used by the enterprise

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

(Interoperability Issues)

Application requirements

A

different applications require different available resources before installing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

(Interoperability Issues)

Software types - In-House developed

A

applications developed internally by the enterprise

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

(Interoperability Issues)

Software types - Commercial

A

programs developed by the third-party organizations such as apple, adobe, and microsoft

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

(Interoperability Issues)

Software types - Tailored commercial

A

almost completely customized right out of the box for an enterprise

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

(Interoperability Issues)

Software types - open source

A

developers of open source software permit anyone to analyze, modify, and distribute the source code for free

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

(Interoperability Issues)

Standard data formats

A

enterprises can address interoperability issues by using standard data formats such as ODF, PDF, TDF, PNG, HTML, CSV, XML, ASCII

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

(Interoperability Issues)

Protocols and APIs

A

protocol and API interoperability challenges can be addressed by using applications that support interoperability-friendly protocols or using a broker service that acts as a middleman to broker what are otherwise incompatible protocols and APIs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

(Resilience issues)

A

focuses on preventing service disruptions, while also quickly detecting and recovering from ones that do occur

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

(Resilience issues)

Use of heterogeneous components

A

refers to systems that use different components

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

(Resilience issues)

Course of action automation/orchestration

A

enterprises can respond to resiliency issues by implementing manual mitigations or using automation task runs, or orchestration systems can automatically take care of them

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

(Resilience issues)

Distribution of critical assets

A

critical assets should be distributed accross systems or locations to minimize the scope of critical asset losses

18
Q

(Resilience issues)

Persistence and non-persistence of data

A
  • Persistent data = data that rarely changes, despite shutdowns
  • Non-persistent data = data that frequently changes or does not remain after shutdowns
19
Q

(Resilience issues)

Redundancy/high availability

A

uses duplication of systems so that a failure of one system will result in the automatic transfer of services to a backup system

20
Q

(Resilience issues)

Assumed likelihood of attack

A

determining the likelihood of attacks takes into consideration both vulnerabilities and the threats themselves

21
Q

(Data Security Considerations)

Data remnants

A

can be destroyed through drive overwriting, degaussing, encryption, or physically destroying drives

22
Q

(Data Security Considerations)

Data aggregation

A

the compilation of data from multiple sources into a summarized report format

23
Q

(Data Security Considerations)

Data isolation

A

process of contolling user access to data that is located in the same environment as other data and users

24
Q

(Data Security Considerations)

Data ownership

A

the data owners knowledge of data types can help with integration by ensuring the enterprise knows who is accountable for making decisions on how certain data should be classified, managed, and used by the enterprise

25
Q

(Data Security Considerations)

Data sovereignty

A

data sovereignty stipulates that once data has been collected on foreign soil, it is subject to the laws of that particular nation

26
Q

(Data Security Considerations)

Data volume

A

too much data increases the attack surface of server since there is more information to be compromised

27
Q

(Resource provisioning and deprovisioning)

Users

A

accounts can be provisioned by a cloud administrator or on-premise administrator, or both, depending on whether the user accounts are cloud-only, federated, or synchronized

28
Q

(Resource provisioning and deprovisioning)

Servers

A

Whether on-premises or in the cloud, servers are increasingly being provisioned as VMs by many enterprises

29
Q

(Resource provisioning and deprovisioning)

Virtual Devices

A

can refer to many things including VMs as well as VM building blocks such as CPUs, RAM, and hard disks

30
Q

(Resource provisioning and deprovisioning)

Applications

A

applications are increasingly being provisioned in the cloud due to the speed of deployment, ease of access, and the simplicity of controlling access to applications

31
Q

(Resource provisioning and deprovisioning)

Data remnants

A

cloud computing environments may have trouble employing comprehensive sanitization methods to data remnants because data is typically located in virtual spaces shared by multiple cloud consumers

32
Q

Design considerations during mergers acquisitions and demergers/divestitures

A
  • whenever corporations restructure it increases vulnerabilities because of confusion
  • security design must take into consideration the procedures involved in restructuring
33
Q

Network secure segmentation and delegation

A
  • entities must be segmented to increase separation of information and resources
  • network segmentation is a basic tool used as part of a defense-in-depth and layered security strategy
34
Q

Logical deployment diagram and corresponding physical deployment diagram of all relevant devices

A
  • logical diagrams are created first. Shows desired connections in network topology
  • physical diagrams show the exact position of placement of network resources
35
Q

(Security implications of integrating enterprise applications)
CRM

A

Customer relationship management model
- models that are typically implemented via a software suite that facilitate interactions with customers, customer service, technical support, and other areas of business

36
Q

(Security implications of integrating enterprise applications)
ERP

A

Enterprise Resource Planning
- business process management software that permits enterprises to use a consolidated platform of business applications modules to manage enterprise wide activities such as customer service, human resource, accounting, sales, payroll, purchase orders, and many more

37
Q

(Security implications of integrating enterprise applications)
CMDBs

A

Configuration Management Databases
-automatically track the state of enterprise assets such as hardware, software, policies, documentations, networks, and staff throughout the lifecycle of these assets

38
Q

(Security implications of integrating enterprise applications)
CMS

A

Content Management Systems
- typically web-based applications that encourage enterprise-wide collaboration with web applications and documentation between multiple contributors creating, editing, and publishing content

39
Q

(Security implications of integrating enterprise applications)
Integration enablers - Directory services

A

directory services are centralized identity access management systems that store information about network objects, in addition to providing authentication, authorization, location, management, and auditing services upon those network objects

40
Q

(Security implications of integrating enterprise applications)
Integration enablers - DNS

A

Domain name system

- critical part of internet infrastructure to mapping names to IP addresses

41
Q

(Security implications of integrating enterprise applications)
Integration enablers - SOA

A

Service Oriented Architecture

- a set of requirements and principles to facilitate the development of interoperable software services

42
Q

(Security implications of integrating enterprise applications)
Integration enablers - ESB

A

Enterprise Service Bus

- a type of architecture for facilitating communications between applications or web services in SOA

CAS-003 (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions