Security Domain Flashcards
I: SECURE 3-TIER APP
Presentation tier
S3 Bucket: Bucket ACLs (read/write, etc.), Encryption (object) – custom key or Amazon default key
CloudFront: OAI (origin access identity), Geo restrictions, Custom headers, Signed URLs, Signed cookies, HTTPS & DDoS
Application tier
API Gateway: Resource policies, Identity pools, Client certificates, Usage plans, Throttling, Caching, API Keys
Lambda: Lambda triggers, Lambda role, Lambda security group, SSM parameter store
Data tier
Amazon RDS: DB security group, DB encryption, Private endpoint, KMS
Additional security
WAF: Layer 7 firewall
I: STATEFUL FIREWALL
Stateful firewall (Security groups) this means any changes applied to an incoming rule will be automatically applied to the outgoing rule. e.g. If you allow an incoming port 80, the outgoing port 80 will be automatically opened. Security group support allow rules only (by default all rules are denied). e.g. You cannot deny a certain IP address from establishing a connection.
I: WAF
WAF (layer 7) is an advanced Firewall system which offers the security from threats, malware, and other vulnerable attacks.
I: IDS
is a system that monitors network traffic for suspicious activity and issues alerts when such activity is discovered.
FireEye
CrowdStrike
Zeek
Snort
I: SSL/TLS HANDSHAKE
Client Hello Server. I want to establish secure communication between the two of us. Here are my cipher suits and compatible SSL/TLS version.
Server Hello Client. I have checked your cipher suits and SSL/TLS version. I think we’re good to go ahead. Here are my certificate file and my public key.
Client Let me verify your certificate. Okay, it seems fine, but I need to verify your private key. What I’ll do is, I will generate and encrypt a pre-master (shared secret key) key using your public key. Decrypt it using your private key and we’ll use this master key to encrypt and decrypt the information
Server Done. Now that both the parties know who they’re talking to, the information transferred between them will be secured using the master-key. Keep in mind that once the verification part is over, the encryption takes place through the master-key only. This is symmetric encryption.
Client I’m sending you this sample message to verify that our master-key works. Send me the decrypted version of this message. If it works, our data is in safe hands
Server Yeah, it works. I think we’ve accomplished what we were looking for.
I: HTTP
used for transferring data over a network. Most information that is sent over the Internet, including website content and API calls, uses the HTTP protocol. There are two main kinds of HTTP messages: requests and responses.
I: TLS/SSL PROCESS
is public key encryption: there are two keys, a public key and a private key, and the public key is shared with client devices via the server’s SSL certificate. When a client opens a connection with a server, the two devices use the public and private key to agree on new keys, called session keys, to encrypt further communications between them.
All HTTP requests and responses are then encrypted with these session keys, so that anyone who intercepts communications can only see a random string of characters, not the plaintext.
I: TLS TERMINATION
SSL should terminate at the load balancer is because it offers a centralized place to correct SSL attacks such as CRIME or BEAST. If SSL is terminated at a variety of web servers, running on different OS’s you’re more likely to run into problems due to the additional complexity. Keep it simple, and you’ll have fewer problems in the long run.
I: HASHING
Meant to verify that a file or piece of data hasn’t been altered, in other words, a checksum.
MD4 MD5 SHA RIPEM WHIRLPOOL TIGER
I: AT REST
it is not traveling within the system or network, and it is not being acted upon by any application or third-party. It’s something that has reached a destination, at least temporarily.
I: CERTIFICATES PROCESS
Your web browser downloads the web server’s certificate, which contains the public key of the web server. It uses this public key to verify that the web server’s certificate was indeed signed by the trusted certificate authority. The certificate contains the domain name and/or ip address of the web server.
I: PKI
is a set of processes, policies, and technology for associating cryptographic keys with the entity to whom those keys were issued.
PKI is made of several elements which are:
Certification Authority (CA) Registration Authority (RA) Certificate Revocation List (CRL) Certification Practice Statement (CPS) Transport Layer Security (TLS)
I: SECURE LOGINS
Secure digital certificates
encryption standards
zero-interaction zuthentication (ZIA)
fingerprint readers
account key feature
trust score system
persona-based authentication
advanced biometrics.
I: SYMMETRIC ENCRYPTION
is a type of encryption where only one key (a secret key) is used to both encrypt and decrypt electronic information.
RC4, AES DES 3DES QUAD Blowfish, etc.
I: CUSTOMER KEYS
Customer master keys (CMKs) You can use a CMK to encrypt and decrypt up to 4 KB (4096 bytes) of data. Typically, you use CMKs to generate, encrypt, and decrypt the data keys that you use outside of AWS KMS to encrypt your data. This strategy is known as envelope encryption. AWS KMS will store keys.