ISO 27001:2022 has 34 technological controls, A.8.1 through A.8.34, in Annex A. This directory covers the full theme: devices, access, information, infrastructure and software development. Each guide explains the control in practical terms, including failures to look for and evidence that a repair has worked.
Guides to all 34 controls
A.8.1
Endpoint protection
Managed laptops and phones need protections that remain effective wherever employees access company information.
A.8.2
Privileged access
Administrator permissions give people and services powerful access that needs limits, approval and periodic review.
A.8.3
Information access
Access rules limit which information each person or service can reach through applications and underlying systems.
A.8.4
Source code access
Repository permissions govern who can read or change source code and use the associated development tools.
A.8.5
Sign-in protection
Authentication checks establish who is requesting access, including through alternative sign-in routes and account recovery.
A.8.6
System capacity
Capacity planning connects resource use and expected demand so systems can continue to support business needs.
A.8.7
Malware defenses
Malware defenses combine technical protection and working practices to prevent, detect and recover from malicious software.
A.8.8
Technical vulnerabilities
Vulnerability management connects known weaknesses to affected assets, treatment decisions and checks that the treatment worked.
A.8.9
Configuration baselines
Configuration management keeps deployed settings aligned with approved baselines as systems, software and networks change.
A.8.10
Information deletion
Deletion controls remove information when retention ends, including copies held across systems and service providers.
A.8.11
Sensitive data masking
Masking limits the sensitive values people can see while preserving the information needed for their work.
A.8.12
Data leakage prevention
Leakage controls detect or restrict routes through which sensitive information could leave its approved locations.
A.8.13
Backup and recovery
Backup coverage and recovery tests establish whether required information can be recovered after loss or damage.
A.8.14
Service redundancy
Backup components keep services available during failure, provided the replacement can operate when the primary component stops.
A.8.15
Event records
Logs preserve relevant system events with enough detail and protection to support investigation and review.
A.8.16
Activity monitoring
Monitoring examines system activity for unusual behavior and directs findings to the people responsible for assessment.
A.8.17
Consistent system time
Aligned system clocks make timestamps comparable when teams reconstruct events across applications, devices and infrastructure.
A.8.18
Powerful system utilities
Utilities that can bypass normal safeguards need restricted access and controlled use for approved maintenance tasks.
A.8.19
Operational software installation
Controlled installation keeps unapproved software off operational systems and identifies who can authorize and install changes.
A.8.20
Network protection
Network safeguards control connections and traffic to protect information moving between systems and services.
A.8.21
Network service security
Network services need agreed security requirements, service expectations and responsibilities that remain clear during operation.
A.8.22
Network separation
Separate network groups limit traffic between users, systems and services with different access or security needs.
A.8.23
Web access filtering
Web filtering restricts access to harmful or inappropriate external sites according to the organization's access policy.
A.8.24
Encryption and keys
Encryption protects information when the methods suit its use and access to the keys remains controlled.
A.8.25
Secure development practices
Development processes include security activities from initial planning through implementation, testing and subsequent changes.
A.8.26
Application security needs
Application requirements specify the protections a new or changed application must provide for its intended use.
A.8.27
Secure system design
Engineering principles guide system architecture so security protections remain consistent as components and connections change.
A.8.28
Code security
Coding practices address weaknesses in implementation and give reviewers consistent expectations for the code they approve.
A.8.29
Development security tests
Security tests examine whether software meets its requirements during development and before acceptance for use.
A.8.30
External development work
Outsourced development needs agreed security expectations and oversight of the supplier's work before it is accepted.
A.8.31
Separate development environments
Development, testing and production have distinct access and data boundaries that protect live systems during engineering work.
A.8.32
System change controls
Change management connects proposed system changes with assessment, authorization and checks on the resulting operation.
A.8.33
Protected test data
Test information needs suitable selection, access and handling so testing does not expose sensitive production data.
A.8.34
Safe audit testing
Audit tests need agreed scope and safeguards that protect operational information and services while testing takes place.
Control drift between audits
A policy can describe a protection that the system has stopped enforcing. Consider a repository whose settings no longer require review before a change. The policy still calls for review, but compliance and engineering now need to trace which releases passed without it.
Repository configuration changes
Review requirement disappears
Changes bypass required review
Ongoing technical control work
ZeroTB takes responsibility for the technical work behind your control commitments. Our team reads the policies and reports, checks systems daily and drafts repairs for your approval. We then verify the repaired state and retain the evidence in a signed Verified Control Record.
Each control gap has an accountable owner
Your team decides on legitimate exceptions
Control records stay in ZeroTB
Talk to our team
We can discuss the technical controls that need repeated attention and how that work affects compliance, IT and engineering.
FAQ
Do all 34 controls apply to our organization?
The selection depends on your risks and requirements. Your Statement of Applicability documents which controls are necessary and why, whether they are implemented, and why any Annex A controls are excluded. The ISO auditing guidance on applicability describes that relationship between risk treatment and control selection.
Where should we start when a change affects several controls?
Use the failed requirement as the starting point. If a deployment gave someone excessive access, both the information access and change management guides can help. ZeroTB relates the gap to your commitments and the affected systems, including cases where several requirements apply to the same repair.
How do vulnerability and configuration management differ?
Vulnerability management deals with technical weaknesses and their treatment under A.8.8. Configuration management, A.8.9, deals with approved system settings. An unsafe setting can create a vulnerability. A software flaw, however, may need treatment even when every setting is correct.
Does collecting logs satisfy the monitoring control?
Logs alone do not establish that monitoring works. A.8.15 covers recording events and protecting those records. A.8.16 concerns examining activity for unusual behavior. For example, a log feed may work correctly while a detection rule fails to identify an event that needs assessment.
Which controls matter when developers use coding agents?
Begin with the access granted to the agent. An agent contributing code brings repository permissions, coding practices, testing and change approval into scope. If it can reach production, configuration and environment separation also need attention. The coding-agent controls page covers these connections in more detail.
What evidence does a completed technical repair leave?
The repair produces a signed Verified Control Record. It contains the requirement, before-and-after state, action, approval and verification, allowing an auditor to follow the work from the original gap to the checked result. See the evidence record page for the contents of this portable record.
Can ZeroTB keep the records for our technical controls?
Yes. ZeroTB keeps the technical control commitments, checks, repairs and audit evidence together. We maintain the underlying controls. A repair may serve several framework requirements where the safeguard and scope align. The frameworks hub lists the programs covered.
Where can we find implementation guidance beyond these summaries?
Use ISO/IEC 27002:2022 for implementation guidance on information security controls. The guides in this directory discuss operation and evidence for individual controls. Our ISO 27001 framework page puts them in the context of the management system and the remaining Annex A themes.
Start with the Pilot
During the eight-week Pilot, we map up to 25 commitments from your report and take two real control gaps through verified restoration. The offer includes working controls and portable evidence records from those completed repairs.