CompTIA Security+ SY0-701 exam preparation glossary. All 5 domains covered. Click any row to expand full definition and contextual example. Press / to search · Esc to clear.
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Categories | Broad classifications describing the nature and purpose of security controls: technical, managerial, operational, and physical. | Controls are categorized as technical, managerial, operational, and physical to streamline implementation. |
| Compensating | Alternative controls that achieve security goals when primary controls are not feasible due to technical or operational constraints. | When full encryption is not possible, strong access controls and logging serve as compensating controls. |
| Control Types | Categories of security mechanisms: preventive, detective, corrective, deterrent, compensating, and directive. | Preventive stops threats; detective identifies incidents; corrective restores systems; deterrent discourages attacks. |
| Corrective | Controls that respond to and rectify security incidents after they have occurred, including patching and policy updates. | Post-breach patching of vulnerabilities and updating security protocols are corrective controls. |
| Detective | Controls that identify and alert organizations to security incidents as they occur through monitoring and analysis. | Intrusion detection systems (IDS) monitor network traffic and alert administrators to suspicious activities. |
| Deterrent | Controls designed to discourage individuals from attempting to breach security measures through visible warnings. | Warning signs about surveillance cameras deter potential intruders from attempting unauthorized access. |
| Directive | Controls that guide employee behavior through policies, procedures, standards, and training programs. | A security awareness training program teaching employees to recognize phishing is a directive control. |
| Managerial | Controls focusing on managing security policies, procedures, and compliance through organizational practices. Also called administrative controls. | Security policies and employee training programs are managerial controls ensuring security protocols are followed. |
| Operational | Controls involving day-to-day operations and processes executed by people to maintain security. | Regular security audits and incident response drills are operational controls supporting effective threat response. |
| Physical | Security measures protecting physical assets and facilities from unauthorized access, theft, or damage. | Key card access systems and biometric scanners restricting server room entry are physical controls. |
| Preventive | Controls aimed at stopping security incidents before they occur through firewalls, encryption, MFA, and access controls. | Antivirus software and regular patch management are preventive controls protecting systems from malware. |
| Technical | Security measures using technology to enforce security policies automatically. Also called logical controls. | Firewalls and TLS encryption are technical controls safeguarding data transmitted over networks. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| AAA | Framework for controlling access: Authentication verifies identity, Authorization grants permissions, Accounting tracks usage. | A bank uses AAA protocols to ensure only authorized users access accounts and all transactions are logged. |
| Availability | Guarantee that systems and data are accessible when needed by authorized users. The 'A' in the CIA triad. | Redundant servers and off-site backups ensure high availability of services during outages. |
| Confidentiality | Principle ensuring sensitive information is not disclosed to unauthorized individuals. The 'C' in the CIA triad. | Encrypting emails containing personal information maintains confidentiality during transmission. |
| Integrity | Assurance that data is accurate and unaltered except by authorized users. The 'I' in the CIA triad. | Hashing files ensures data integrity, allowing users to verify a file has not been modified since creation. |
| Non-Repudiation | Security principle preventing individuals from denying their actions related to data or transactions. | Digital signatures provide non-repudiation, proving the sender sent a specific message or transaction. |
| Zero Trust | Security model requiring strict identity verification for every access request regardless of network location. "Never trust, always verify." | In zero-trust environments, all access requests are authenticated and authorized even for internal users. |
| Gap Analysis | Comparing actual security performance with desired performance to identify discrepancies and improvement areas. | A company evaluates its cybersecurity measures against industry best practices to identify shortfalls. |
| Honeypot | A decoy system designed to attract and detect unauthorized access attempts, capturing attacker tools and techniques. | A honeypot mimics a vulnerable server to monitor attacker behavior and gather threat intelligence. |
| Honeynet | A network of honeypots simulating a real environment to capture a broader range of attack behavior data. | Security researchers deploy honeynets to study APTs by observing how attackers move across multiple decoy systems. |
| Honeyfile | A file planted in a system that appears valuable but is designed to alert administrators when accessed. | A file labeled "Confidential Financial Data" triggers an alert if any user attempts to open it. |
| Honeytoken | A piece of data appearing legitimate that serves as a trap to detect unauthorized access or misuse. | A fake user account (honeytoken) lets security teams monitor unauthorized attempts to use stolen credentials. |
| Access Badge | A physical card containing encoded credentials that authenticates the holder and grants access to controlled physical spaces. | Employees scan badges at entry points to unlock doors to secure areas within an office. |
| Access Control Vestibule | An enclosed interlocking door system preventing tailgating. Also called a mantrap. | Corporate offices use vestibules with security guards to verify identities before allowing entry into secured areas. |
| Bollards | Short, sturdy vertical posts that control vehicle access and protect infrastructure from vehicle-borne attacks. | Bollards in front of government buildings prevent unauthorized vehicle entry and protect against ramming attacks. |
| Video Surveillance | CCTV and IP camera systems providing continuous monitoring, recording, and deterrence. | Retail stores use video surveillance systems to deter theft and provide evidence of security incidents. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Allow / Deny Lists | Allow lists explicitly permit only approved entities; deny lists block known-bad entities. | An allow list permits only trusted IP addresses to access internal applications, blocking everything else. |
| Backout Plan | A predefined strategy for reversing changes if an implementation fails or causes adverse effects. | A backout plan restored previous configurations after a new security software deployment caused system instability. |
| Maintenance Window | A pre-approved time period — often nights or weekends — during which changes can be applied with minimal business impact. | An organization scheduled a weekend maintenance window to apply critical security patches to all servers. |
| Standard Operating Procedure | Step-by-step instructions outlining how to perform specific tasks to ensure consistency and quality in operations. | An SOP for incident response provides detailed steps for detecting, reporting, and addressing security incidents. |
| Version Control | A system tracking changes to documents or code over time, enabling rollback to known-good states and providing audit trails. | Version control helps teams track changes to security documentation, ensuring everyone uses the most current information. |
| Impact Analysis | A systematic assessment of how a proposed change could affect business operations, security posture, and compliance. | Conducting an impact analysis before implementing new security measures helps ensure minimal disruption to critical operations. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Asymmetric Encryption | Encryption using a mathematically linked key pair (public/private). Data encrypted with the public key can only be decrypted by the private key. | Asymmetric encryption allows secure data exchange without sharing private keys, enhancing security. |
| Symmetric Encryption | Encryption using the same key for both encryption and decryption. Faster than asymmetric; AES is the standard. | Symmetric encryption is faster than asymmetric and used for encrypting large amounts of data like files or databases. |
| Hashing | A one-way mathematical function producing a fixed-length digest of any input. Used for password storage and integrity verification. | Hashing passwords ensures the actual passwords remain unrecoverable even if the database is compromised. |
| Salting | Adding a random unique value to each password before hashing to defeat rainbow table and dictionary attacks. | Salting passwords before hashing prevents attackers from using rainbow tables to crack password hashes. |
| Digital Signatures | Provides authentication, integrity, and non-repudiation by hashing a message and encrypting with the sender's private key. | Digital signatures confirm an email is from the claimed sender and has not been altered during transmission. |
| PKI | The complete system of hardware, software, policies, and procedures that manages digital certificates and public-private key pairs. | PKI is used in secure email communication, ensuring only intended recipients can decrypt messages. |
| Certificate Authorities | Trusted third parties that issue, sign, and revoke digital certificates in the PKI hierarchy. | Certificate authorities provide SSL/TLS certificates to websites, enabling secure encrypted connections. |
| Hardware Security Module | A tamper-resistant hardware device providing secure key generation, storage, and cryptographic operations. Keys never leave in plaintext. | Financial institutions use HSMs to safeguard sensitive transaction data and cryptographic keys. |
| Trusted Platform Module | A dedicated microcontroller chip on the motherboard providing hardware-based security: key generation, storage, and platform integrity measurement. | Computers use TPM to ensure secure boot and provide hardware-based encryption capabilities like BitLocker. |
| Tokenization | Substitutes sensitive data with randomly generated tokens stored in a token vault, dramatically reducing data breach impact. | Tokenization replaces credit card numbers with unique tokens in payment processing, reducing PCI scope. |
| Steganography | Conceals the existence of a message by embedding it within ordinary-looking files (images, audio, video) without altering visible appearance. | A secret message can be concealed within an image file without altering its visible appearance. |
| Key Stretching | Applies hash functions repeatedly (PBKDF2, bcrypt, Argon2) to a weak key to produce a stronger derived key, slowing brute-force attacks. | Key stretching makes brute-force attacks harder by increasing the computational time needed to test each key. |
| Full-Disk Encryption | Encrypts the entire contents of a storage device including OS, applications, and user data. Protects against physical device theft. | Full-disk encryption on laptops safeguards all data if the device is lost or stolen. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Nation-State | Government-sponsored groups conducting long-term APT campaigns for intelligence collection and geopolitical advantage. Most sophisticated threat actors. | A nation-state actor orchestrates attacks to steal intellectual property and boost domestic industries. |
| Organized Crime | Professional criminal enterprises with specialized roles: access brokers, ransomware developers, negotiators, and money laundering networks. | Organized crime syndicates execute ransomware attacks on healthcare providers, demanding hefty ransoms. |
| Hacktivist | Politically or socially motivated hackers using DDoS, defacement, and data leaks to advance their cause. | A hacktivist collective defaces a government website during a political protest to draw public attention. |
| Insider Threat | A current or former employee, contractor, or partner who uses authorized access to harm the organization. Bypasses perimeter controls. | A disgruntled employee steals customer data before leaving the company and plans to sell it to competitors. |
| Unskilled Attacker | Also called script kiddies. Use automated tools that lower the attack barrier, primarily targeting unpatched vulnerabilities. | An unskilled attacker uses publicly available exploit tools to attack unsecured websites with common CVEs. |
| Shadow IT | IT systems, devices, or services used by employees without IT department approval, creating security gaps and compliance violations. | Employees using unapproved cloud storage expose sensitive company data to potential security breaches. |
| Data Exfiltration | The unauthorized movement of data from within an organization to an external destination. A primary objective of many cyberattacks. | An insider threat secretly copies client lists to a USB drive, planning to sell the data to competitors. |
| Espionage | Covert collection of sensitive information from adversaries or competitors through long-term, stealthy APT campaigns. | A nation-state infiltrates a rival corporation's network to steal trade secrets and gain competitive advantage. |
| Financial Gain | The most common motivation for cyberattacks, driving ransomware, BEC fraud, credit card theft, and sale of stolen data. | Organized crime targets financial institutions with phishing schemes to steal account credentials and transfer funds. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Phishing | Mass social engineering attacks sent to broad audiences. Spear phishing targets specific individuals; whaling targets executives; vishing is via phone. | A phishing email mimicking a bank deceives users into entering credentials on a fake website. |
| Vishing | Voice phishing conducted via phone calls using pretexting, urgency, and authority to manipulate targets into divulging information. | A vishing call from "tech support" tricks victims into providing remote system access or personal details. |
| Smishing | SMS-based phishing exploiting higher open rates and lower suspicion associated with text messages. | A smishing message from a fake bank urgently requests account verification via a link to a fraudulent website. |
| Business Email Compromise | Sophisticated scam targeting businesses where attackers impersonate executives using spoofed or compromised email accounts. Causes billions in annual losses. | An attacker impersonates a CEO via email, requesting a wire transfer to a fraudulent account. |
| Supply Chain Attack | Attacks targeting less-secure elements in a supply chain to compromise the ultimate target through trusted relationships. SolarWinds is the prime example. | A breach at an MSP exposes its client companies as attackers gain access through a trusted third party. |
| Watering Hole Attack | Attackers compromise a website frequently visited by the intended target to deliver malware to specific visitors. | Attackers compromise an industry website to infect visitors from a specific target organization with tailored malware. |
| Typosquatting | Registers misspelled or visually similar domain names to intercept users who make typing errors. Also called URL hijacking. | An attacker registers "goolge.com" hoping users mistype "google.com" and visit the malicious fake site. |
| Removable Device (USB Drop) | Physical media used to introduce malware into secure systems. Autorun features can execute malware immediately upon connection. | A USB stick labeled "Confidential Report" found in a parking lot installs malware when plugged in. |
| Default Credentials | Factory-set credentials publicly documented and not changed during deployment. Especially problematic in IoT devices and network equipment. | IoT devices with unchanged default credentials allow attackers easy access to their settings and capabilities. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Zero-Day | A vulnerability unknown to the vendor with no available patch. Highly valued in criminal and nation-state markets. | Zero-day vulnerabilities allow attackers to exploit systems without fear of detection or patching, causing widespread damage. |
| SQL Injection | Injects malicious SQL code through user input fields. Can extract data, bypass authentication, or execute OS commands. Prevention requires parameterized queries. | An attacker sends malicious SQL commands to a web application, exposing sensitive customer data from the database. |
| Cross-Site Scripting (XSS) | Injects malicious client-side scripts into web pages viewed by other users. Types: reflected, stored, and DOM-based. | An attacker embeds harmful JavaScript in a webpage; any visitor's browser executes it, potentially stealing their session cookies. |
| Buffer Overflow | A program writes more data to a memory buffer than it can hold, overwriting adjacent memory and potentially allowing arbitrary code execution. | An attacker feeds excessive data into an input field, causing the application to crash or execute malicious code. |
| Misconfiguration | Incorrect settings in software, networks, or devices. One of the most common vulnerability categories and often the root cause of major breaches. | A firewall misconfiguration leaves sensitive data accessible to unauthorized users, causing a compliance breach. |
| VM Escape | Exploits hypervisor vulnerabilities to break out of a VM's isolation boundary, gaining code execution on the host or other VMs. | A VM escape vulnerability allows an attacker to move from a compromised VM to the host system. |
| Race Condition / TOCTOU | Vulnerability arising when system behavior depends on the timing of events. Attacker changes state between check (TOC) and use (TOU). | An attacker alters a file after validity is checked but before it is used, leading to unauthorized actions. |
| End-of-Life (EOL) | The point at which a vendor ceases providing security updates. All vulnerabilities discovered after EOL remain permanently unpatched. | End-of-life devices are attractive targets because they lack security patches for known vulnerabilities. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| DDoS | Uses a botnet of compromised devices to flood targets with traffic. Types include volumetric, protocol, and application-layer attacks. | Thousands of compromised devices flood a company's web server with traffic, crashing it and making it inaccessible. |
| Brute Force | Exhaustive search attack trying all possible combinations. Mitigated by MFA, account lockout, and strong passwords. | A hacker systematically tries thousands of password combinations until successfully gaining admin account access. |
| Malware | Malicious software including viruses, worms, trojans, ransomware, spyware, adware, rootkits, and keyloggers. | Ransomware encrypts an organization's files and demands payment in cryptocurrency for the decryption key. |
| Ransomware | Malware that encrypts victim files and demands ransom for the decryption key. Often deployed via phishing or RDP exploitation. | A hospital's files are encrypted; attackers demand $1M in Bitcoin before providing the decryption key. |
| Rootkit | Malware that hides its presence by modifying the OS at a deep level. Extremely difficult to detect and remove. | A rootkit hides malicious processes from the OS task manager, allowing persistent unauthorized access to go undetected. |
| Birthday Attack | Cryptographic attack exploiting probability to find two different inputs producing the same hash. Used to forge digital signatures. | A birthday attack enables an attacker to discover two messages with the same hash, breaking digital signature security. |
| Man-in-the-Middle (MitM) | Attacker secretly intercepts and potentially alters communications between two parties who believe they are communicating directly. | On public Wi-Fi, an attacker intercepts traffic between a user and their bank, capturing login credentials. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Cloud Computing | Delivery of computing services over the internet. Models: IaaS, PaaS, SaaS. Deployments: public, private, hybrid, community. | A company migrates its email server to Microsoft 365 (SaaS), eliminating on-premises infrastructure management. |
| Hybrid Cloud | Combines on-premises infrastructure with public cloud resources, allowing data and applications to move between environments. | A bank keeps customer data on private servers while using public cloud for burst compute workloads during tax season. |
| Serverless Architecture | Cloud model where the provider manages infrastructure; developers deploy code as functions. Shifts OS/runtime security responsibility to the provider. | A company deploys payment processing logic as AWS Lambda functions, eliminating server patch management. |
| Microservices | Architecture where applications are built as small, independent services communicating via APIs. Each service has its own security boundary. | An e-commerce app splits into separate services for payments, inventory, and user auth, each requiring its own security controls. |
| Containerization | Packages applications and their dependencies into isolated containers (Docker, Kubernetes). Containers share the host OS kernel, creating shared attack surface. | Developers use Docker containers to ensure consistent security configurations across development and production environments. |
| Infrastructure as Code | Managing and provisioning infrastructure through machine-readable configuration files rather than manual processes. Enables security as code. | A company uses Terraform to define security group rules as code, ensuring consistent configuration across all cloud deployments. |
| SASE | Converges WAN networking and network security functions (CASB, FWaaS, ZTNA, SWG) into a unified cloud-delivered service. | A distributed company uses SASE to provide consistent security policies for remote employees regardless of location. |
| SD-WAN | Software-Defined Wide Area Network that uses software to control network connectivity, replacing or augmenting traditional MPLS connections. | A retail chain uses SD-WAN to securely connect hundreds of store locations with centralized security policy management. |
| Shared Responsibility Model | Defines which security tasks are the cloud provider's responsibility versus the customer's, varying by service model (IaaS/PaaS/SaaS). | In AWS IaaS, AWS secures the physical data center; the customer is responsible for OS patches and application security. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Network Segmentation | Dividing a network into isolated segments to contain breaches, reduce attack surface, and improve compliance. | A hospital separates its clinical systems, guest Wi-Fi, and administrative network into distinct VLANs with firewall enforcement. |
| DMZ | A perimeter network segment between the internet and internal network hosting public-facing servers. Provides an additional security layer. | Web servers are placed in the DMZ so internet users can access them without direct access to internal databases. |
| Firewall | Network security device monitoring and controlling incoming/outgoing traffic based on predefined security rules. Types: packet-filtering, stateful, NGFW, WAF. | A next-generation firewall inspects application-layer traffic and blocks attempts to exploit web application vulnerabilities. |
| IDS / IPS | Intrusion Detection System monitors and alerts; Intrusion Prevention System actively blocks detected threats. Both use signature and anomaly-based detection. | An IPS automatically blocks network traffic matching known attack signatures before it reaches internal servers. |
| VPN | Creates an encrypted tunnel over an untrusted network. Types: site-to-site (connecting offices) and remote-access (connecting individuals). | Remote employees use VPN to securely access corporate resources over public internet connections. |
| Proxy Server | An intermediary between clients and the internet. Forward proxies protect clients; reverse proxies protect servers. Can perform SSL inspection and content filtering. | A company's forward proxy filters web traffic, blocking malicious sites and enforcing acceptable use policies. |
| Load Balancer | Distributes incoming network traffic across multiple servers to ensure high availability and prevent any single server from becoming a bottleneck. | A load balancer distributes web traffic across five servers, ensuring service continuity if one server fails. |
| NAC | Enforces security policy compliance before granting network access. Checks device health, OS patch level, antivirus status, and user identity. | NAC prevents a laptop with outdated antivirus from connecting to the corporate network until remediated. |
| VLAN | Logical segmentation of a physical network at Layer 2. Groups devices regardless of physical location; isolates broadcast domains. | A company places all IoT devices on a separate VLAN, preventing compromised devices from reaching corporate servers. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Data Classification | Categorizes data by sensitivity level to apply appropriate security controls. Common levels: public, internal, confidential, restricted. | A company labels documents as Public, Internal, Confidential, or Top Secret, applying stricter controls to higher classifications. |
| DLP | Technology monitoring, detecting, and blocking unauthorized transmission of sensitive data via email, web, or removable media. | DLP software alerts security when an employee tries to email a file containing credit card numbers to an external address. |
| Data at Rest | Inactive data stored on physical media: hard drives, databases, backups, or cloud storage. Protected by encryption and access controls. | Customer records stored in a database are encrypted at rest using AES-256, protecting them from storage media theft. |
| Data in Transit | Data moving between systems over a network. Protected by transport encryption protocols like TLS to prevent interception. | HTTPS encrypts web traffic between users and servers, protecting credentials and personal data from eavesdropping. |
| Data in Use | Data actively being processed in memory. Hardest to protect; threats include memory scraping attacks and cold boot attacks. | Secure enclaves (Intel SGX) process sensitive computations in isolated memory that the OS cannot access. |
| Rights Management | Controls how data can be used, copied, printed, or forwarded even after it has been shared. Persists with the document regardless of location. | IRM prevents a confidential document recipient from forwarding, printing, or copy-pasting its contents. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| High Availability | System design ensuring continuous operation with minimal downtime using redundancy, failover, and clustering. Often expressed as uptime percentages (99.999% = 5 nines). | A critical application runs on an HA cluster; if one node fails, another automatically takes over within seconds. |
| Redundancy | Duplicating critical system components so that backup components can take over when the primary fails. | Dual power supplies in a server ensure it continues operating if one power supply fails. |
| RAID | Redundant Array of Independent Disks. Combines multiple drives for performance, redundancy, or both. Key levels: RAID 0 (striping), RAID 1 (mirroring), RAID 5 (striping+parity), RAID 6, RAID 10. | RAID 5 allows a database server to continue operating and recover data after a single hard drive fails. |
| Backup Types | Full (all data), Incremental (changes since last backup), Differential (changes since last full backup). 3-2-1 rule: 3 copies, 2 media types, 1 off-site. | A company runs full backups weekly and incremental backups nightly, reducing backup windows while ensuring recoverability. |
| Disaster Recovery | Documented plans and procedures for restoring IT systems after a disaster. Key metrics: RTO (recovery time) and RPO (data loss tolerance). | A company's DR plan activates a warm standby site when the primary data center is destroyed, restoring operations within 4 hours. |
| RTO | The maximum acceptable time to restore operations after a disruption. Defines how long a system can be offline before the impact is unacceptable. | The e-commerce platform has an RTO of 2 hours, meaning it must be restored within that timeframe to avoid major revenue loss. |
| RPO | The maximum acceptable amount of data loss measured in time. Defines how frequently backups must occur to meet business requirements. | An RPO of 15 minutes means the company can lose at most 15 minutes of transactions in a disaster scenario. |
| Geographic Dispersal | Distributing systems across physically separate locations to protect against regional disasters, power outages, and natural events. | A cloud provider runs three geographically separated availability zones so a regional hurricane cannot cause total outage. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Integrations and APIs | Utilizing APIs to automate interactions between different software applications, enabling seamless data exchange and task execution. | An automation script updates user information across multiple applications using API calls whenever there is a change to ensure consistency. |
| Reaction Time | The speed at which organizations can respond to incidents or changes, significantly enhanced through automation and SOAR platforms. | Automated alerts notify the security team of potential threats in real time, enabling quicker responses to mitigate risks. |
| Resource Provisioning | The automated assignment of computing resources — storage, memory, processing power — based on predefined criteria. | A cloud service automatically allocates additional storage space for a department when their usage reaches a certain threshold. |
| Scaling Securely | The ability to grow infrastructure while automatically applying security measures to newly provisioned resources to maintain compliance. | As user demand increases, additional cloud resources are automatically provisioned with security policies pre-applied. |
| Security Groups | Collections of users or devices sharing the same security policies, making it easier to manage permissions and access control at scale. | A security group for the finance team allows members to access financial applications while restricting access for other departments. |
| Single Point of Failure | A potential risk where a single failure in an automated process could lead to complete system failure or loss of functionality. | If the automation tool that provisions user accounts fails, no new employees can be onboarded until the issue is resolved. |
| Standard Infrastructure Configs | Maintaining uniformity in system setups to ensure security and operational effectiveness, facilitated by automated configuration management. | New servers are automatically configured with security settings defined in templates to ensure consistency. |
| Technical Debt | The future costs of shortcuts or compromises in automation that may require rework or additional effort later. | An organization that opts for quick automation solutions might face the need to revise those solutions later, incurring more costs. |
| Ticket Creation | The automated process of generating support tickets for incidents or requests, ensuring efficient tracking and management of issues. | An automated system creates a support ticket whenever a user reports an issue via email, ensuring IT can promptly track the problem. |
| User Provisioning | Automated creation, management, and deactivation of user accounts and permissions to ensure timely and appropriate access to resources. | When a new employee is onboarded, their user account is automatically created and they receive access to essential applications. |
| Workforce Multiplier | The concept of increasing workforce effectiveness through automation, allowing fewer staff to achieve greater operational results. | A small IT team can manage a complex infrastructure effectively due to automation tools, maximizing productivity without additional hires. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Preparation | The initial incident response phase focusing on planning, training, and establishing resources and protocols to handle potential incidents. | Conducting training sessions for the incident response team to familiarize them with their roles before an incident occurs. |
| Detection | Identifying and recognizing potential security incidents through monitoring and analysis of systems, networks, and data. | A SIEM system alerts the security team to unusual network activity indicating a possible breach. |
| Containment | Actions taken to limit the impact of a security incident and prevent further damage or data loss. | During a malware outbreak, the IT team isolates affected systems from the network to stop the spread of infection. |
| Eradication | Removing the cause of a security incident from the environment — malware, attacker persistence mechanisms, and exploited vulnerabilities. | After confirming a breach, the security team identifies and removes the malicious software used by the attackers. |
| Recovery | Restoring affected systems and data to normal operations following an incident, ensuring systems are clean and secure before returning to service. | After eradicating a threat, the organization restores data from backups and conducts testing before going live. |
| Lessons Learned | Post-incident review identifying what worked well and what can be improved in the incident response process for future events. | After a security incident, the team holds a meeting to discuss the response's effectiveness and updates their incident response plan. |
| Digital Forensics | Application of forensic techniques to collect, preserve, and analyze electronic data to support security incident investigations. | A digital forensics team retrieves and analyzes logs from compromised servers to understand the scope of a data breach. |
| Chain of Custody | The documented process of maintaining and handling evidence to ensure its integrity and admissibility in legal proceedings. | Documenting each time evidence is accessed or transferred ensures chain of custody remains intact for legal purposes. |
| Acquisition | Collecting and securing data and evidence from systems while maintaining integrity and chain of custody. Bit-for-bit copies preserve original data. | Investigators create bit-by-bit copies of hard drives to preserve original data for analysis while ensuring evidence integrity. |
| Legal Hold | Preserving relevant information and data for legal purposes, preventing alteration or deletion during an investigation or litigation. | An organization places a legal hold on all data related to a security breach to ensure evidence is preserved for potential legal action. |
| Root Cause Analysis | Systematic process identifying the underlying causes of incidents to prevent future recurrence by addressing vulnerabilities. | After a data breach, the security team determines how attackers gained access and what security measures failed. |
| Tabletop Exercise | A discussion-based exercise where team members review and discuss responses to simulated incident scenarios to identify process strengths and weaknesses. | Organizing a tabletop exercise involving senior management to discuss their roles during a data breach and evaluate communication plans. |
| Threat Hunting | Proactive search for indicators of compromise within an organization's network to identify threats before they cause damage. | Security analysts review network traffic patterns to detect suspicious activity that automated systems might miss. |
| Simulation | A practical exercise that mimics real-world incidents, allowing teams to practice responses in a controlled environment and evaluate effectiveness. | Running a simulated ransomware attack where teams must respond to a series of challenges to practice incident response skills. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Application Logs | Records created by applications documenting events, transactions, and errors that occur during operation. Useful for troubleshooting and performance monitoring. | An application log shows a series of error messages when a user attempts to access a feature that is currently down for maintenance. |
| Endpoint Logs | Logs from endpoint devices tracking user activity, system events, software installations, and security incidents. Crucial for endpoint security analysis. | An endpoint log includes details about software installations, user logins, and any detected malware activities on the device. |
| Firewall Logs | Logs generated by firewalls tracking allowed and denied network traffic based on predefined rules. Help identify access attempts and policy violations. | A firewall log entry indicates an attempt to access a restricted port, prompting the security team to investigate further. |
| IPS/IDS Logs | Logs from Intrusion Prevention/Detection Systems tracking suspicious activities and potential security incidents based on signatures and anomaly detection. | An IDS log captures an alert for a detected port scan, prompting security analysts to investigate the source of the scanning activity. |
| Network Logs | Logs from networking devices (routers, switches) providing insights into traffic patterns, connection attempts, and network performance. | A network log shows the volume of data transmitted to and from specific IP addresses, helping identify unusual traffic spikes. |
| OS Security Logs | Security logs generated by the operating system recording authentication attempts, system events, and configuration changes. Help identify breaches and unauthorized access. | Windows Security Event logs record user logins, failed access attempts, and changes made to system security settings. |
| Metadata | Data providing information about other data — creation dates, file sizes, access permissions, author, GPS coordinates embedded in files. | Metadata associated with log files includes timestamps, authors, and file formats, which help organize and retrieve logs during analysis. |
| Dashboards | Visual interfaces aggregating and displaying key security metrics from various sources for real-time monitoring and analysis. | A SOC dashboard displays real-time alerts, incident statistics, and system health metrics, allowing analysts to prioritize responses. |
| Automated Reports | Predefined reports generated by security tools summarizing findings, trends, and metrics related to security events and compliance. | A weekly automated report from a SIEM includes statistics on detected incidents, response times, and trends over the past week. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Acceptable Use Policy | A document outlining acceptable activities and restrictions for using an organization's systems and resources. | Employees must adhere to the AUP, which prohibits using company devices for unauthorized activities like personal file downloads. |
| Data Owners | Individuals or entities responsible for data who make decisions about access, usage, and classification. | The department head acts as the data owner, defining who can access specific datasets within the company's CRM system. |
| Data Custodians | Individuals who maintain the integrity, security, and availability of data within an organization as directed by data owners. | IT administrators function as data custodians, ensuring that data is securely stored and regularly backed up. |
| Data Controllers | Entities that determine how personal data is processed and for what purpose. Accountable under GDPR and similar privacy laws. | As the data controller, the company decides how customer information is collected, processed, and used for marketing. |
| Data Processors | Entities that process data on behalf of the data controller under their instructions. | A cloud service provider acts as a data processor, storing and managing customer data according to the controller's instructions. |
| Governance Structures | The framework of authority and decision-making within an organization, which can be centralized or decentralized. | The company's governance structure includes a central board that makes key strategic decisions and committees that oversee specific operations. |
| Playbooks | Step-by-step guides detailing responses to specific incidents such as phishing, ransomware, or data breaches. Reduce decision fatigue during incidents. | The incident response team follows a playbook to manage phishing attacks, isolating compromised accounts and conducting forensic analysis. |
| Onboarding/Offboarding | Processes for integrating new employees (provisioning access) and securely removing access when they leave the organization. | HR ensures new hires have proper access through onboarding, while IT handles offboarding by revoking all access when an employee exits. |
| Password Standards | Guidelines defining the complexity, length, and management requirements for passwords. Modern standards (NIST SP 800-63B) emphasize length over complexity. | The organization enforces password standards requiring a minimum of 12 characters with a mix of character types. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Risk Assessment | Evaluation of identified risks based on their severity and likelihood of occurrence to prioritize mitigation efforts. | The company conducts an annual risk assessment to prioritize threats like data breaches and system downtime based on potential impact. |
| Risk Appetite | The overall amount of risk an organization is willing to accept in pursuit of its objectives. | With a conservative risk appetite, the company avoids high-risk investments and focuses on protecting existing assets. |
| Risk Mitigation | Actions taken to reduce the likelihood or impact of a risk. Implements controls addressing the vulnerability or threat. | The company mitigates the risk of unauthorized access by implementing multifactor authentication across all systems. |
| Risk Transfer | Shifting the financial responsibility for managing a risk to another party, such as through cyber insurance. | The company purchases cyber insurance to transfer the financial risk of a potential data breach to the insurer. |
| Risk Avoidance | A strategy where the organization eliminates the risk entirely by not engaging in the risky activity. | The company avoids the risk of third-party cloud storage by opting to store sensitive data entirely in-house. |
| Risk Acceptance | The decision to take no additional action to mitigate a risk and accept the potential consequences. Must be documented and approved. | The company accepts the risk of minor outages during system updates, deciding that the potential downtime is manageable. |
| Quantitative Risk Analysis | A numerical evaluation of risks using financial metrics. Key formulas: SLE × ARO = ALE. Enables cost-benefit analysis of security investments. | Using quantitative analysis, the team estimates the annual cost of a potential server failure at $100,000 in lost revenue. |
| Qualitative Risk Analysis | Assessing risks based on subjective judgment, expert opinions, and relative scales (high/medium/low) rather than financial metrics. | The company conducts qualitative analysis through interviews with stakeholders to assess how a data breach would affect customer trust. |
| Business Impact Analysis | Identifies the potential effects of disruptions on business operations. Establishes RTO and RPO requirements for critical systems. | The BIA shows that a 24-hour power outage could disrupt production and lead to significant financial losses. |
| Risk Register | A documented record of identified risks, their severity, assigned owners, and how they will be managed. Living document updated continuously. | The company updates its risk register after each risk assessment, tracking new cybersecurity threats and mitigation strategies. |
| SLE | The expected monetary loss for a single occurrence of a risk event. Formula: SLE = Asset Value × Exposure Factor. | The SLE for a stolen laptop is $2,000, based on the cost of the hardware and the value of the data that could be lost. |
| ALE | The expected annual monetary loss due to a specific risk. Formula: ALE = SLE × ARO. Used to justify security control investments. | The ALE for phishing attacks is $50,000, calculated based on the frequency and financial impact of incidents. |
| MTBF | The average time interval between failures of a system during operation. A measure of reliability and availability planning. | The MTBF for new servers is 12 months, suggesting they are expected to operate without failure for approximately one year between incidents. |
| MTTR | The average time required to repair a failed system or component. Measures operational response efficiency. | The MTTR for critical servers is 4 hours, meaning the IT team is expected to restore them within that time. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Vendor Assessment | The process of evaluating the risk and security posture of a vendor or third party before entering a business relationship. | Before selecting a cloud storage provider, the company performs a thorough vendor assessment including penetration testing and audit reviews. |
| Due Diligence | The thorough investigation conducted before entering a formal agreement to evaluate a vendor's financial health, legal history, and security measures. | As part of vendor selection, the company performs due diligence to evaluate the vendor's financial health and security measures. |
| SLA | A contract specifying the expected level of service including performance metrics, availability guarantees, and remedies for failure to meet targets. | The SLA with the vendor outlines a 99.9% uptime guarantee, with penalties if this level is not maintained. |
| NDA | A legal contract that prohibits the sharing of confidential information disclosed during a business relationship or evaluation. | The company requires all vendors to sign an NDA to protect its proprietary information during the vendor evaluation process. |
| MOU | A non-binding agreement outlining the terms and conditions of an understanding between parties before committing to a formal agreement. | The company signs an MOU with a potential vendor to explore a partnership before committing to a formal agreement. |
| MSA | A long-term contract outlining general terms and conditions under which future work orders will be completed, eliminating renegotiation for each project. | The MSA allows the company to enter into multiple projects with the vendor without negotiating a new contract each time. |
| Right-to-Audit | A contract provision granting the organization the ability to audit the vendor's processes and systems to verify compliance with security standards. | The vendor agreement includes a right-to-audit clause, allowing the company to verify vendor compliance with security standards at any time. |
| Supply Chain Analysis | The process of identifying and assessing security risks throughout the vendor's supply chain, including sub-processors and component suppliers. | The company conducts a supply chain analysis to ensure all vendors producing hardware components adhere to strict security standards. |
| Vendor Monitoring | Continuously evaluating a vendor's performance and compliance after the contract is in place to ensure ongoing adherence to security standards. | After signing the contract, the company regularly monitors the vendor's security practices and service levels to ensure SLA compliance. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Compliance Reporting | Documenting and submitting reports to demonstrate adherence to legal, regulatory, and internal requirements. | The company prepares both internal and external compliance reports to ensure it meets all regulatory standards and internal policies. |
| Non-Compliance Consequences | The penalties or adverse effects resulting from failing to comply with legal, regulatory, or contractual obligations. | Failing to meet data protection requirements can lead to significant fines and reputational damage. |
| Data Inventory & Retention | Cataloging what data exists and determining how long data should be kept based on regulatory or business requirements. | The company maintains a detailed data inventory and retention schedule to ensure compliance with legal requirements. |
| Right to Be Forgotten | The right of individuals to request deletion of their personal data from an organization's records (GDPR Article 17). | Customers exercise their right to be forgotten, and the company deletes their personal data from its systems accordingly. |
| Global Privacy Laws | International laws governing data protection and privacy, requiring organizations to adhere to multiple jurisdictional requirements simultaneously. | The company adjusts its global operations to meet privacy requirements across the EU, US, and other regions. |
| Data Subject | An individual whose personal data is collected, stored, or processed by an organization. Has rights under privacy laws including access and deletion. | As a data subject, customers have the right to access and request deletion of their personal information. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Penetration Testing | Authorized simulated attack on systems to identify vulnerabilities before malicious actors can exploit them. Types: black box, white box, gray box. | The IT team conducts a penetration test to find potential weak points in the organization's security defenses. |
| Reconnaissance | Information gathering phase of penetration testing. Passive (observing public data) or active (directly interacting with the target). | The penetration testing team spends several days gathering details about the company's network before launching test attacks. |
| Third-Party Audit | An objective audit conducted by an outside firm to verify compliance, financial accuracy, or effectiveness of internal controls. | The company hires an independent third-party firm to audit its security protocols and provide an objective assessment. |
| Self-Assessments | Internal evaluations where an organization reviews its own processes, controls, and adherence to regulations or policies. | The IT department conducts self-assessments to identify potential security vulnerabilities before the external audit. |
| Attestation | Formally affirming or verifying that certain standards or requirements have been met, often through internal or external review and sign-off. | The company provides attestation of its compliance with industry standards through a formal audit conducted by an independent firm. |
| Rules of Engagement | Guidelines outlining acceptable behavior and interactions during penetration tests or audits, including scope, timing, and restricted systems. | The company defines rules of engagement with its vendor before conducting a penetration test, specifying what systems can be assessed. |
| TERM | DEFINITION | CONTEXTUAL EXAMPLE |
|---|---|---|
| Phishing Campaigns | Coordinated simulated phishing attacks used to test and train employees to recognize and report phishing attempts. | The security team sends simulated phishing emails quarterly to measure and improve employee click-through rates. |
| Social Engineering | A tactic where attackers manipulate individuals into divulging confidential information or performing actions that compromise security. | An employee encounters social engineering when a caller pretends to be from IT support, attempting to extract login credentials. |
| Insider Threat Awareness | Training employees to recognize indicators of insider threat behavior — both malicious and unintentional — and to report concerns appropriately. | The security team monitors user activities to identify potential insider threats from employees with access to sensitive information. |
| OPSEC | A risk management process that protects sensitive information by identifying and addressing vulnerabilities in day-to-day operations. | The company implements operational security measures, restricting access to sensitive data and training employees on information hygiene. |
| Password Management | Best practices and tools for creating, storing, and managing secure passwords to prevent unauthorized access. | Employees participate in password management training, learning to create strong passwords and use password managers effectively. |
| Anomalous Behavior Recognition | Identifying actions that deviate from normal patterns — potentially indicating risky, unexpected, or malicious activities. | The security team detects anomalous behavior when an employee attempts to access sensitive files at unusual hours from an unknown location. |
| Situational Awareness | Being aware of one's environment and recognizing potential threats or vulnerabilities in real time, both physical and digital. | Employees improve their situational awareness during training, learning to spot social engineering tactics and suspicious behaviors. |
| Removable Media Risks | Portable devices like USB drives and external hard drives must be securely managed to prevent data exfiltration and malware introduction. | Employees receive guidelines on the risks associated with using unsecured removable media and secure data transfer practices. |
| Hybrid/Remote Work Security | Work environments where employees work both on-site and remotely, requiring additional security measures to manage associated risks. | The organization updates its security policies to address challenges specific to hybrid environments, focusing on securing home networks. |
No terms matched your search criteria — try different keywords or clear the filter