Domain 3: Implementation (25%) Flashcards
*3.2 Endpoint protection
Data Loss Prevention (DLP)
Monitors the data of a system while in use, in transit, or at rest to detect attempts to steal the data.
*Software or hardware solutions
*3.2 Boot Integrity
Unified Extensible Firmware Interface (UEFI) (Updated version of BIOS)
Firmware that provides the computer instructions for how to accept
input and send output.
A type of system firmware providing support for 64-bit CPU
operation at boot, full GUI and mouse operation at boot, and
better boot security.
*3.2 Self-encrypting drive (SED)
Storage device that performs whole disk encryption by using embedded
hardware.
*hardware based
*3.2 Full-disk encryption (FDE)
software based encription.
Mac: FileVault
Windows: BitLocker
*3.2 Trusted Platform Module (TPM)
Chip residing on the motherboard that contains an encryption key.
If your motherboard doesn’t have TPM, you can use an external
USB drive as a key.
*3.3 Network appliances
Hardware Security Module (HSM)
Physical devices that act as a secure cryptoprocessor during the encryption process
you’ll see them as an adapter card that plugs in through a USB or a network-attached device.
*3.2 Endpoint protection
Endpoint Detection and Response (EDR)
A software agent that collects system data and logs for analysis by a monitoring system to provide early detection of threats.
*3.2 Endpoint protection
Antivirus/anti-malware
Software capable of detecting and removing virus infections and (in most
cases) other types of malware, such as worms, Trojans, rootkits, adware,
spyware, password crackers, network mappers, DoS tools, and others.
*3.2 Endpoint protection
Host-based firewall/personal firewall
A software application that protects a single computer from unwanted Internet traffic.
ex: Windows: windows firewall
Mac: PF and IPFW
Linux: iptables
*3.5 Mobile device management (MDM)
Remote Wipe
Remotely erases the contents of the device to ensure the information is
not recovered by the thief.
*3.1 Protocols
Transport Layer Security
puts an encryption layer and a tunnel between your device and the server to ensure you have confidentiality and nobody is conducting a man-in-the-middle attack from you.
*3.5 Mobile Device Management (MDM)
Centralized software solution that allows system administrators to create and enforce policies across its mobile devices.
-remote administration and configuration of mobile devices. I can push out software policies to you, prevent you from installing applications, and install updates remotely without your use.
*3.7 Account policies
Geotagging
Embedding of the geolocation coordinates into a piece of data (i.e., a photo).
*3.5 Mobile Device Management (MDM)
Storage Segmentation (BYOD)
Creating a clear separation between personal and company data on a single device.
*3.5 Deployment Models
BYOD
Bring your own device
*3.5 Deployment Models
CYOD
Choose your own device
CYOD gives the employee a choice of a couple of phones.
*3.2 Hardware root of trust
A cryptographic module embedded within a computer system that can endorse trusted execution and attest to boot settings and metrics.
EX: Trusted Platform Module (TPM), Hardware Security Module (HSM).
*3.2 Trusted Platform Module (TPM)
A specification for hardware-based storage of digital certificates, keys,
hashed passwords, and other user and platform identification
information.
you really need to remember that TPM, the trusted platform module, is this part of your system
that allows you to have the ability to ensure that when you’re booting up, it is done securely and we can take those reports and digitally sign them using the TPM.
3.3, 3.5, 3.8
Hardware Security Module (HSM)
An appliance for generating and storing cryptographic keys that is less susceptible to tampering and insider threats than software-based storage.
3.2 Boot Integrity
Secure boot
Secure boot is a feature of UEFI that prevents unwanted processes from executing during the boot operation. Essentially, as a computer is booting up, it’s going to check things and make sure that there’s digital signatures installed from those operating system vendors. If Microsoft Windows isn’t signed by Microsoft, we’re not going to boot it. That’s the idea of secure boot. We want to make sure that the bootloader is only loading things that are valid and not loading malware.
*3.2 Boot Integrity
Measured Boot
A UEFI feature that gathers secure metrics to validate the boot process in an attestation report. So, as you’re booting up, it’s going to be taking different measurements, how much time does it take for you to do this? How much process should it take to do that, and based on that, it’s going to collect that data, it’s going to create a report, and then it’s going to attest to it.
*3.2 Boot Integrity
Boot Attestation
A claim that the data presented in a report is valid, and it does this by digitally signing it using the TPM’s private key. So, the UEFI, it’s going to take that report, it’s going to sign it with that digital key, and then send it on to the operating system into the processor. This way we know we can trust it.
- 3.2 Application Security
Static code analysis
Source code of an application is reviewed manually or with automatic
tools without running the code
Think of static analysis as your third grade English teacher looking over your essay and marking it up with a red pen to show you all of your errors.
*3.2 Application Security
Dynamic code Analysis
Analysis and testing of a program occurs while it is being executed or run
Dynamic analysis on the other hand is performed on a program while it’s being run. The most common type of dynamic analysis includes the use of fuzzing.