4.1 Secure enterprise architecture Flashcards
(42 cards)
Adapt data flow security to meet changing business needs
- enterprises must adapt to the needs of the enterprise
- must start with strong security foundations to allow for easier and faster updates
(Standards)
mandatory requirements in support of a policy
- HIPAA, PCI DSS, NIST 800 series
(Standards)
Competing standards
two or more standards available to us to address the same issues
(Standards)
Lack of standards
new technologies that lack standards, such as IoT devices and blockchain
(Standards)
De facto standards
standards that are so widely accepted by an industry but have not undertaken formal standardization process
(Interoperability Issues)
Legacy systems and software/current systems
legacy systems are older applications and hardware that are no longer supported by the vendor, but are still used by the enterprise
(Interoperability Issues)
Application requirements
different applications require different available resources before installing
(Interoperability Issues)
Software types - In-House developed
applications developed internally by the enterprise
(Interoperability Issues)
Software types - Commercial
programs developed by the third-party organizations such as apple, adobe, and microsoft
(Interoperability Issues)
Software types - Tailored commercial
almost completely customized right out of the box for an enterprise
(Interoperability Issues)
Software types - open source
developers of open source software permit anyone to analyze, modify, and distribute the source code for free
(Interoperability Issues)
Standard data formats
enterprises can address interoperability issues by using standard data formats such as ODF, PDF, TDF, PNG, HTML, CSV, XML, ASCII
(Interoperability Issues)
Protocols and APIs
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
(Resilience issues)
focuses on preventing service disruptions, while also quickly detecting and recovering from ones that do occur
(Resilience issues)
Use of heterogeneous components
refers to systems that use different components
(Resilience issues)
Course of action automation/orchestration
enterprises can respond to resiliency issues by implementing manual mitigations or using automation task runs, or orchestration systems can automatically take care of them
(Resilience issues)
Distribution of critical assets
critical assets should be distributed accross systems or locations to minimize the scope of critical asset losses
(Resilience issues)
Persistence and non-persistence of data
- Persistent data = data that rarely changes, despite shutdowns
- Non-persistent data = data that frequently changes or does not remain after shutdowns
(Resilience issues)
Redundancy/high availability
uses duplication of systems so that a failure of one system will result in the automatic transfer of services to a backup system
(Resilience issues)
Assumed likelihood of attack
determining the likelihood of attacks takes into consideration both vulnerabilities and the threats themselves
(Data Security Considerations)
Data remnants
can be destroyed through drive overwriting, degaussing, encryption, or physically destroying drives
(Data Security Considerations)
Data aggregation
the compilation of data from multiple sources into a summarized report format
(Data Security Considerations)
Data isolation
process of contolling user access to data that is located in the same environment as other data and users
(Data Security Considerations)
Data ownership
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