Plain language

Glossary

74 terms

  • Air gap

    A physical separation with no network path. It is strong until someone carries data across on a laptop or a USB stick.

    Communication and Network Security

  • Attribute-based access control

    Access decided from attributes of the user, the resource, and the context, such as location, time, and data sensitivity.

    Identity and Access Management

  • Bell-LaPadula

    A confidentiality model: no reading up, and no writing down. It protects secrets more than it protects accuracy.

    Security Architecture and Engineering

  • Biba

    An integrity model: no reading down, and no writing up. It keeps untrusted data from contaminating trusted data.

    Security Architecture and Engineering

  • Brewer-Nash

    A model that prevents conflicts of interest by limiting what a subject can see based on what they have already accessed. It is sometimes called the Chinese Wall.

    Security Architecture and Engineering

  • Business impact analysis

    A study of which processes matter, how fast they must return, and what they depend on. It feeds continuity priorities.

    Security and Risk Management

  • Chain of custody

    A record of who collected, held, and transferred evidence, so a later reviewer can trust it was not altered.

    Security Operations

  • Change management

    The path a proposed change takes through request, review, approval, and rollback planning. It is not the same thing as installing a patch.

    Security Operations

  • Clark-Wilson

    An integrity model built on well-formed transactions and separation of duties, closer to how a business ledger actually works.

    Security Architecture and Engineering

  • Clearing

    Overwriting media so ordinary tools cannot recover the data. It may not defeat a lab with specialist equipment.

    Asset Security

  • Cold site

    A space with power and cooling but little or no ready equipment. It is cheaper and slower.

    Security Operations

  • Compensating control

    A substitute that reduces risk when the preferred control cannot be used. It should be documented as an exception, not treated as the new standard.

    Security and Risk Management

  • Configuration baseline

    The known, approved build of a system. Drift is the gap between that picture and what is actually running.

    Security Operations

  • Corrective control

    A control that repairs damage or restores a normal state, such as a patch after an incident or a restored backup.

    Security and Risk Management

  • Data controller

    The party that decides why and how personal data is processed. Privacy law often puts the duties on this role.

    Asset Security

  • Data custodian

    The person or team that protects information day to day according to the owner's rules. They operate systems; they do not invent the classification.

    Asset Security

  • Data owner

    The business leader accountable for a set of information: its classification, who may use it, and how long it is kept.

    Asset Security

  • Data processor

    A party that handles personal data for a controller, under the controller's instructions. A payroll vendor is a common example.

    Asset Security

  • Data remanence

    Data that remains after a casual delete. It is why disposal has to match the sensitivity of the media.

    Asset Security

  • Defense in depth

    Several independent layers so one failure does not open the whole environment. Layers should fail differently, not repeat the same mistake.

    Security Architecture and Engineering

  • Destruction

    Making media unusable, such as shredding or incinerating it, when reuse is not worth the residual risk.

    Asset Security

  • Detective control

    A control that notices an event, such as a log review, an alarm, or a reconciliation.

    Security and Risk Management

  • DevSecOps

    Building security checks into the same pipeline that builds and ships software, instead of a late review that the release will skip.

    Software Development Security

  • Discretionary access control

    The owner of an object can grant access. It is flexible and easy to make too loose.

    Identity and Access Management

  • Due care

    The ongoing effort a reasonable organization makes to protect people and information, such as writing a policy and funding the control it names.

    Security and Risk Management

  • Due diligence

    The investigation before a decision, such as checking a vendor or a merger target, so leaders can show they looked before they leapt.

    Security and Risk Management

  • Duress

    A signal that a person is being forced. The response should protect the person first, not announce that the alarm was spotted.

    Security Operations

  • Dynamic application security testing

    Testing a running application from the outside. It sees behavior and can miss code that the test never reaches.

    Software Development Security

  • East-west traffic

    Traffic between systems inside the environment. A flat network lets an intruder move here with little resistance.

    Communication and Network Security

  • Ethical disclosure

    Telling the responsible party about a flaw in a way that lets them fix it, rather than publishing a recipe for harm.

    Security Assessment and Testing

  • Fail secure

    When a control breaks, it should deny access or stop the unsafe action. A door that unlocks in a fire is a deliberate exception for life safety.

    Security Architecture and Engineering

  • False negative

    A real problem the test or the monitor missed. It is usually more dangerous than a noisy false alarm.

    Security Assessment and Testing

  • False positive

    An alert or finding that looks bad and is not. Too many of them teach people to ignore the system.

    Security Assessment and Testing

  • Federation

    Letting one organization accept identity assertions from another, so people are not issued a second password for every partner.

    Identity and Access Management

  • Full interruption test

    Production is stopped and the recovery site takes the load. It is the most realistic test and the most disruptive.

    Security Operations

  • Hot site

    A recovery site that is equipped and nearly ready, so restoration is measured in hours rather than weeks.

    Security Operations

  • Just-in-time access

    Privilege that is granted for a short window and a stated task, then removed, instead of a standing admin account.

    Identity and Access Management

  • Key custody

    Who can use, escrow, or recover a cryptographic key. The algorithm does not matter if the wrong person holds the key.

    Security Architecture and Engineering

  • Least privilege

    Giving a person, service, or process only the access required for the current job, and no standing extra.

    Security Architecture and Engineering

  • Lessons learned

    A deliberate review after an incident or a test that changes the plan, the control, or the training. A meeting with no change is just a meeting.

    Security Operations

  • Mandatory access control

    The system enforces labels. Users cannot simply share an object because they feel like it.

    Identity and Access Management

  • Maximum tolerable downtime

    The longest a process can be stopped before the harm becomes unacceptable to the mission.

    Security and Risk Management

  • Micro-segmentation

    Small, policy-based segments, often around a workload, so two servers on the same subnet are not automatically trusted.

    Communication and Network Security

  • Nonrepudiation

    Evidence that a party cannot credibly deny sending or approving something. Digital signatures are a common tool, not the whole idea.

    Security Architecture and Engineering

  • North-south traffic

    Traffic that enters or leaves a boundary, such as users coming in from the internet or data going out to a partner.

    Communication and Network Security

  • Parallel test

    Recovery systems are brought up alongside production, which keeps running. You learn if the spare works without betting the business on it.

    Security Operations

  • Penetration test

    An authorized attempt to achieve a stated goal the way an adversary might, so leaders can see impact rather than a raw list of flaws.

    Security Assessment and Testing

  • Preventive control

    A control that stops an unwanted event, such as a lock, a segregation of duties, or an allow-list.

    Security and Risk Management

  • Provisioning

    Creating access when someone joins or changes role. The matching duty is to remove it when they leave.

    Identity and Access Management

  • Purging

    A stronger sanitization meant to stop laboratory recovery. Degaussing magnetic media is one method.

    Asset Security

  • Recovery point objective

    The amount of data, measured in time, you can afford to lose. It drives how often you back up or replicate.

    Security Operations

  • Recovery time objective

    The target time to restore a process or system after a disruption. It should be shorter than the time the business can actually survive.

    Security Operations

  • Residual risk

    The risk that remains after you have treated it. Insurance, a control, or a decision to accept it does not make this number zero.

    Security and Risk Management

  • Risk

    The chance that a threat will exploit a weakness and cause harm the organization cares about. It is not the threat and not the weakness by themselves.

    Security and Risk Management

  • Risk acceptance

    A conscious choice by the risk owner to live with the remaining risk. It should be written down and revisited, not shrugged off.

    Security and Risk Management

  • Risk appetite

    The amount and type of risk leaders are willing to pursue to meet the mission. It is a board-level choice, not a technician's preference.

    Security and Risk Management

  • Risk avoidance

    Stopping the activity that creates the risk. You do not store card data if you can send customers to a processor instead.

    Security and Risk Management

  • Risk mitigation

    Reducing likelihood or impact with a control. Training, a firewall, and a backup are mitigations.

    Security and Risk Management

  • Risk tolerance

    The acceptable variation around appetite. A team can run a little hot or cold without asking the board to rewrite the strategy.

    Security and Risk Management

  • Risk transfer

    Shifting some financial impact to another party, often by contract or insurance. The operational problem usually stays with you.

    Security and Risk Management

  • Role-based access control

    Access granted through job roles. It scales well and goes stale when roles are not reviewed after people move.

    Identity and Access Management

  • Scoping

    Removing a baseline control that does not apply, such as a wireless control on a system with no radio.

    Asset Security

  • Service account

    An identity used by a system, not a person. It needs an owner, a purpose, and a way to rotate its secret.

    Identity and Access Management

  • Single sign-on

    One authentication that opens several applications. It is convenient and concentrates the value of that one login.

    Identity and Access Management

  • Software bill of materials

    A list of the components in a piece of software. You cannot answer a supplier question about a library you did not know you shipped.

    Software Development Security

  • Software composition analysis

    Identifying libraries and other third-party components, and the known flaws or license duties that come with them.

    Software Development Security

  • Static application security testing

    Reviewing source or bytecode without running the program. It finds some flaws early and misses flaws that appear only at runtime.

    Software Development Security

  • Synthetic transaction

    A scripted action, such as a test login or a fake purchase, used to learn whether a service still works before customers complain.

    Security Assessment and Testing

  • Tabletop exercise

    A discussion-based test of a plan. People talk through a scenario. Nothing in production is actually failed over.

    Security Operations

  • Tailoring

    Adjusting a baseline control so it fits the system, without quietly dropping the intent of the baseline.

    Asset Security

  • Threat

    A person, event, or condition that could cause harm if it reaches a weakness. A storm, a thief, and a failed disk are all threats.

    Security and Risk Management

  • Vulnerability

    A weakness that a threat can use. Missing patches, shared admin passwords, and a door that does not latch are vulnerabilities.

    Security and Risk Management

  • Vulnerability assessment

    A search for known weaknesses. It lists what is wrong. It does not, by itself, prove an attacker could chain those weaknesses into harm.

    Security Assessment and Testing

  • Zero trust

    A design that does not treat a network location as proof of trust. Each request is checked for identity, device, and need.

    Security Architecture and Engineering