Security Architecture and Engineering Flashcards
Secure Design Principles
Least Privilege
Defence in depth
secure defaults
fail securely
Seperation of duties (SOD)
Keep it simple and small
Zero trust
Secure access service edge
privacy by design
trust but verify
shared responsibility
least privilege (PoLP)
individuals are only be granted access necessary to perform their required functions
PoLP
Seperation of duties (SOD)
designed to limit risk associated with critical functions/transactions
Risk mitigation : by requiring multiple individuals in carrying out sensitive transactions
Defence in depth
uses multiple layers of overlapping controls to provide security
key concept: any one control may fail but all controls will not fail (hopefully)
Eg: Client pC
Patching, hardening, antivirus, app whitelisting, host based firewall, HIP etc
Secure Defaults
means systems and applications are delivered in their most secure state
- some settings may be relaxed later after thorough risk analysis
Fail securely
Note: It is usually better to lose functionality rather than security
means a system that encounters a critical error or failure will ‘fail closed’ as opposed to failing open
Eg: Older unix systems would often fail open in the case of critical damage to the disk
- A system reboots, detects damaged disk sectors, and tries to automatically repair via fsck command (file system check)
- if this system failed to repair, the system would boot to a single user console session, automatically logged in as root (superuser)
- this is violation of fail securely
Keep it simple and small (KISS)
A design maxim
emphasizes that simple designs are more secure than complex designs
more complexity is equal to more attack surface
As systems becomes more interconnected, security will get worse
Zero trust
Removes the concept of internal is trusted, external is not
assume that all traffic is untrusted
build security into the DNA of IT architecture by investing in situational awareness, and developing robust vuln and incident mgmt capabilities
3 concepts of zero trust
ensure all resources are accessed securely regardless of location
Adopt a least privilege strategy, n strictly enforce access control
inspect and log all traffic
Key network components of zero trust
SDN
Network virtualization
Perimeter design versus
zero trust
Traditional single perimeter defence, everything behind the firewall is trusted
Zero trust defence focusses on resource protection ( nothing is trusted)
The ‘implicit trust zone’ shrinks as much as possible from the entire private network down to an individual comp system or very small cluster
Access is granted thru a policy decision point (PDP), and corresponding policy enforcement point (PEP)
ZERO TRUST provides a set of principles/concepts around moving the PEPs/PDPs closer to the resources.
Note: Idea is to explicitly authenticate and authorise all subjects, assets, workflows that make up the enterprise
SASE - Secure access service edge
SASE architecture combines networking and security as a service functions into a single cloud delivered service at the network edge
delivers converged network and security as a service capabilities, including
SD-WAN
SWG
NGFW,
CASB
ZTNA
Trust, but Verify
- considered a middle step between traditional perimeter defences and zero trust
- focuses on forensic integrity of data n systems, requiring accountability via strong authentication, and enhanced logging
- states that actions on a network should be undeniable, certifiable, and tamper evident
Privacy by design
framework based on embedding privacy into the design and operation of IT systems, n/w infra, and business practices
privacy by design - 7 foundational principles
proactive not reactive
privacy as the default setting
privacy embedded into design
full functionality
end to end security
visibility and transparency
respect for user privacy
Shared responsibility
used by cloud providers like amazon, azure, google
