A guardrail, also called a security control or safeguard, is a countermeasure that protects an organization’s assets. It reduces a vulnerability, makes a threat less likely to succeed, or limits the harm if an incident occurs. Controls help preserve confidentiality, integrity, and availability: keeping information appropriately private, accurate, and accessible. section 1.1.5 section 3.1
Choose a control for the asset and the risk, not simply because the control is available. First identify the asset’s vulnerabilities and relevant threats; then assess the risk and select measures that reduce its likelihood or impact. The goal is an acceptable level of risk, not the elimination of every possible risk. Weigh the protection gained against cost, usability, and disruption to operations. section 1.1.5 section 2.2.3 section 3.0
Guardrails can be grouped by how they work:
- Physical controls protect facilities and tangible assets; examples include locks, access badges, and cameras. section 1.1.5 section 3.2
- Technical controls protect systems and data; examples include firewalls, encryption, and intrusion detection systems. section 3.2
- Administrative controls guide people and processes; examples include policies, procedures, and awareness training. section 1.1.5
Match the guardrail to the asset
A company laptop may need a strong password or multi-factor authentication. A public-facing website may need secure coding, a web application firewall, and monitoring. Neither asset is protected by choosing a control in isolation; its threats and vulnerabilities shape the combination. section 3.1
Controls also have different jobs: they may prevent an incident, detect one, deter an attacker, correct damage, direct behavior, or compensate for a weakness. Layering controls is called defense-in-depth. If one layer fails, another may still prevent, detect, or help respond to the incident. section 3.2.5 section 3.3
|
Physical
|
Technical
|
Administrative
|
|
|
Preventive
|
Door lock
|
Antivirus
software
|
Security
awareness training
|
|
Detective
|
Security
cameras
|
Intrusion
Detection System (IDS)
|
Regular
security audits
|
|
Corrective
|
Fire
suppression systems
|
Automated
system restores points
|
Disaster
Recovery Plan
|
|
Deterrent
|
Barbed wire
fences
|
Login
warning banners
|
Acceptable
Use Policy
|
|
Directive
|
“Authorized
Personnel Only” sign
|
File storage
policy enforcement
|
Standard
Operating Procedures (SOP)
|
|
Compensating
|
Isolating a
legacy server in a secured room
|
Jump server
for accessing a legacy system
|
Additional
approval requirements for access to an unpatched critical system
|
The table pairs each control function with physical, technical, and administrative examples, showing why both its job and its method matter. section 3.2.5






















