Domain 3 - Security Architecture and Engineering Flashcards
Zero Trust Security
○ Addresses limitations of legacy network perimeter-based security model
○ Treats user identity as the control plane
Assumes compromise/ breach in verifying every request, no entity is trusted by default, verify identity, manage device, manage apps, protect data
Secure defaults (secure design principles)
default configuration reflects a restrictive and conservative enforcement of security policy, taken from NIST 800-160
Fail securely (secure design principles)
default configuration reflects a restrictive and conservative enforcement of security policy, taken from NIST 800-160
Trust but verify (secure design principles)
depends on initial authentication process to gain access to the internal “secured” environment then relied on generic access control methods, taken from NIST 800-160, given way to zero trust
Privacy by design (secure design principle)
making privacy and integral part of every system, tech, policy, and design process
§ Proactive and not reactive approach
§ Privacy as the default setting
§ Privacy embedded into design, not added later
§ Privacy should be positive-sum approach, not zero-sum, needs of everybody are met
§ End to end full lifecycle data protection
§ Visibility and transparency, i.e. privacy policy explaining what company does with data
Keep privacy user-centric, i.e. in GDPR the customer can request data and tell them to “forget” them
Security-aaS
cloud provider concept in which security is provided to an org through and online entity
internet of things (IoT)
class of devices connected to internet in order to provide automation, remote control, or AI processing in home or business, plugs, thermostats, speakers, etc
SIEM
sec information and event management, collects data from many sources, provides real time monitoring, traffic analysis of potential attacks, often use AI, ML and threat intel
SOAR
sec orchestration automation and response, threat specific playbooks, response may be fully automated or single click, domain 8, delivered with SIEM typically
Microservices
fine grained services with a discrete function, more modern version of SOA to cloud computing, run on Docker/ kubernetes
SOA (service oriented architecture)
creation of discrete services that may be accessed by users in black box fashion (don’t know whats going on under the hood)
code level vulnerabilities
should be identified early in development lifecycle via static code analysis and dynamic testing to identify deficiencies before release
containerization
lightweight, granular, portable way to package apps for multiple platforms, reduces overhead of server virtualization by enabling containerized apps to run on a shared OS kernel, containers don’t have their own OS, sharing OS of host, test focuses on devops security (container level) and application level security (Authentication and Authorization)
API
set of exposed interfaces allow for program interaction between services, REST uses HTTPS for web comms to offer API end points, all comms between client and server should be encrypted and access limited with API keys, storage/ dist/ transmission of access keys should be done in secure fashion
Embedded Systems
tech component of an IOT device, full computer system embedded inside a larger system, ie printers/ drones/ semi autonomous vehicles, consider authentication practices to ensure they meet security best practices (avoid implied trust)
high performance computing
alternative to client/ server computing model for intensive operations with large data sets, for problems that require large-scale parallel processing, SETI project where individuals can volunteer their compute time i.e. grid computing
grid computing
employs a centralized controller that makes computing assignments to grid members, secure the grid controller
edge computing
some compute operations require processing activities to occur locally not in the cloud, common in IOT scenarios like agricultural, science/ space, military, ie watering plants in a field by sensing moisture, kiosk in a drug store, consider encryption, spoofing protection and authentication
fog computing
places gateway devices in the field to collect and correlate data centrally at the edge, version of edge computing
Serverless (Function as a service FaaS)
different that PaaS, more granular, less decisions around service tier and scale, azure functions and AWS Lambda
IaaS
CSP: networking, storage, servers, virtualization
You: OS, middleware, runtime, data, apps
PaaS
CSP: networking, storage, servers, virtualization, OS, middleware, runtime
You: data, apps
SaaS
CSP: networking, storage, servers, virtualization, OS, middleware, runtime, data, apps
You: n/a
Public cloud
everything runs on CSPs hardware, advantages include scalability, agility, pay as you go, no maintenance, low skills
Private cloud
cloud environment in your own datacenter, legacy support (can support older versions vs public which will typically always be latest versions), control, compliance
Hybrid (cloud model)
combines public and private allowing every app to run in the right location, connect the 2 clouds with VPN, flexible in legacy, compliance, and scalability
CASB
cloud access security broker, security policy enforcement solution, ie ensuring specific users only use the applications we have in place, prevent sensitive information from being shared externally, solves problem of shadow IT
Post quantum cryptography
development of new kinds of cryptographic approaches that can be implemented using todays conventional computers, but will be resistant to quantum computing attacks of the future
Symmetric encryption (shared key)
bulk encryption, fast, holds up well to quantum, uses 1 shared secret key
Grovers algorithm
quantum computer speeds up attacks to halve the key length, 256 bit key is as strong against quantum as 128 bit
Shors algorithm
quantum can easily break all commonly used PK alogorithms, RSA is vulnerable, Elliptic curve is vulnerable, Lattice offers some resistance against quantum
lattice
makes up most publications on post-quantum cryptography, QUANTUM RESISTANT
Stream cipher
symmetric key, one character at a time
Block cipher
crypto key and algo are applied to a block of data at once as a group
Substitution cipher
replace each character with a different character
transposition
rearrange the letters of a plaintext message to form ciphertext
Initialization vector (IV)
random bit string (nonce) that is XORed with the message to reduce predictability and repeatability, same length as the block size or as large as the encryption key
Caesar, vigenere, one-time pad
similar STREAM ciphers, difference is key length, caeser=1, vigenere=longer key like a word/ sentence, one-time pad=same length as the message
one time pad
key must be generated randomely, as long as message to be encrypted, pads be protected against disclosure, pad must be used one-time then discarded
zero knowledge proof
communication concept, specific type of info is exchanged but no real data is transferred, ie digital signature and digital certificate, enables one to prove knowledge of a fact without revealing the fact
split knowledge
information/ priv required to perform an operation is divided among multiple users, ensures no single person has sufficient priv to compromise security, role seperation
work function
aka work factor, measure strength of crypto system by measuring cost/ time to decrypt, work function rating typically represents the amount of time to complete a brute-force attack against a crypto system, TIME AND EFFORT TO BREAK A PROTECTIVE MEASURE
key security
crypto keys provide security to crypto system, modern systems utilize keys of at least 128 bits
symmetric encryption
shared secret key, faster, lacks support for scalability/ easy key distro/ nonrepudiation
AES > block > 128
Blowfish > 64
DES > block > 64 > weak
3DES > block > 64 > moderate
RC4 > stream cipher
RC5 > RSA block mode cipher > 32/63/128 > VERY strong
Skipjack > 64
Twofish > 128
Asymmetric
PKI for communication between parties, supports scalability, easy key distribution, and nonrepudiation, public and private key pairs, stronger than symmetric, encrypt with recipients public key, digital signature signed with own private key
RSA > key transport > 512 > strong
Diffie Hellman > key exchange > moderate
El Gamal > key exchange > very strong
ECC > elliptic curve > very strong
Electronic Codebook Mode (ECB)
DES/3DES mode
simplest and least secure, 64-bit blocks, easy to break
Cipher block chaining (CBC)
DES/3DES mode
each block of unencrypted text is XORed w/ block of ciphertext immediately preceding. Decryption process simply decrypts ciphertext and reverse the XOR operation,
Cipher feedback (CFB)
streaming version of CBC, works on data in real time, uses chaining so errors propogate
Output feedback (OFB)
operates similar to CFB but XORs plaintext with a seed value, no chaining function so errors do not propogate
Counter (CTR)
incrementing value instead of a seed, errors do not propogate
XOR Cipher
exclusiveOR, flipping bits in a simple systemic fashion, when values match = 1, when values don’t match = 0.
Key clustering
weakness where plaintext message generates identical ciphertext message using same algo but different keys, similar to hash collision, same reason why MD5 is no longer used
Hash functions
allow input of any length, provide fixed length output, easy to compute hash function, must be irreversible, must be collision free. MD5 not used anymore, sha-256 is the standard
HMAC - variable hash value length > very strong
MD5 > 128 > weak
SHA1 > 160 > weak
SHA2 > 256 > strong > current standard
SHA3 > 384 > strong
SHA5 > 512 > strong
Salt
random data added before hashing, reduces effectiveness of rainbow table attacks`
Digital signature standard (DSS)
uses SHA-1, SHA-2 (must use SHA-256 these days), and SHA-# message digest functions, works with Digital signature algo (DSA), Rivest, Shamir, Adleman (RSA) algo, and Eliptic Curve DSA (ECDSA) algo, FIPS-186-4 (digital signature standard)
PKI
Certificate authorities (CAs) generate digital certificates containing public keys of system users, Users then distribute certificates to people with whom they want to communicate, recipients verify a certificate using CAs public key, used for web/ network/ email security
Email encryption
standards for encrypted messages include S/MIME and Pretty Good Privacy (PGP)
Web encryption
standard is HTTP over TLS (HTTPS), this has replaced SSL
Network encryption
Ipsec is standard
IPsec
secure communication over IP, transport mode or tunnel mode, establish direct communication between computers or over VPN, windows OS can Ipsec between computers, uses 2 protocols - Authentication header (AH) and encapsulating security payload (ESP)
Meet in the middle attack
exploits protocols using 2 rounds of encryption
Man in the middle attack
fools both parties into communicating with the attacker instead of directly with each other
Birthday attack
attempts to find collisions in hash functions
Replay attack
attempt to reuse authentication requests
Digital rights management (DRM)
allows content owners to enforce restrictions, common in entertainment ie music/ movies/ books, occasionally found in enterprise to protect sensitive info
Rivest, Shamir, and Adleman (RSA)
most famous public key crypto system
El Gamal
Public key cryptosystem, Based on Diffie-Hellman key exchange, less common than RSA
Elliptic Curve
public key cryptosystem, provides more security than other algos with same length key
Security Model
formalize security policy, implemented by enforcing integrity, confidentiality, or other controls, lay out broad guidelines (not specific), up to the developer to decide how models will be integrated into specific designs, map abstract statements into sec policy, determines what subjects can access system and what objects they will have access to
Simple security property (sec model)
describes rules for read, subject cannot read data at a higher classification level (no read up)
Star * security property (sec model)
describes rules for write
Invocation property (sec model)
rules around invocation (calls), such as to subjects
State machine (sec model)
system that is always secure no matter what state its in, based on finite state machine (FSM), “state” is a snapshot of a system at a moment in time, all state transitions must be evaluated, if each transition results in a secure state then the system is a “secure state machine”,