ISO 27001 Controls Explained: A Practical Guide for Businesses

Introduction

Imagine your company stores customer information in the cloud, employees access business systems remotely, and several third-party vendors handle sensitive data. Everything seems to be working well until someone asks a simple question:

“How do you know your information is secure?”

That is where ISO 27001 intervenes.

ISO/IEC 27001:2022 provides requirements for establishing, implementing, maintaining, and continually improving an Information Security Management System (ISMS). It takes a risk-based approach to protecting information across people, processes, and technology.

One of the most discussed parts of the standard is Annex A, which contains a set of 93 information security controls in the 2022 edition. But understanding ISO 27001 controls is not about memorizing 93 items. It is about understanding your risks, selecting appropriate safeguards, implementing them effectively, and maintaining evidence that they work.

What Are ISO 27001 Controls?

In simple terms, ISO 27001 controls are safeguards that organizations can use to reduce information security risks.

For example, if employees can access sensitive customer information, access controls can help ensure that only authorized people can reach it.

If a company faces the risk of a data breach, controls related to vulnerability management, logging, monitoring, and incident management can help reduce or manage that risk.

The 2022 edition of Annex A organizes its 93 controls into four categories:

  • Organizational controls – 37
  • People controls – 8
  • Physical controls – 14
  • Technological controls – 34

This is an important distinction: ISO 27001 is broader than its Annex A controls. The standard defines the requirements for an ISMS, while Annex A provides a reference set of security controls that organizations can consider as part of their risk treatment.

The Four Categories of ISO 27001 Controls Explained

1. Organizational Controls

These controls focus on how information security is managed across the organization.

They cover areas such as information security policies, roles and responsibilities, supplier relationships, threat intelligence, incident management, and business continuity.

Example: A company may define who is responsible for responding to a cybersecurity incident. When an incident occurs, employees know who should investigate it, who should communicate with customers, and who should make key decisions.

2. People Controls

People can be an important part of an organization’s security posture. People controls address areas such as screening, security awareness, training, and responsibilities when employees change roles or leave.

Example: An employee receives security awareness training and learns how to identify a phishing email. Training does not eliminate phishing risk, but it can help employees recognize and report suspicious activity.

3. Physical Controls

Information security is not limited to computers and cloud environments. Physical controls help protect offices, equipment, devices, and areas where sensitive information is stored or processed.

They cover areas such as physical entry, equipment protection, secure disposal, and protection against environmental threats.

Example: A server room may use restricted access so that only authorized personnel can enter it.

4. Technological Controls

These are the controls most people associate with cybersecurity.

They cover areas such as access management, authentication, malware protection, vulnerability management, logging, backup, network security, and secure development.

Example: A company may use multi-factor authentication and role-based access to ensure that employees cannot access systems or information beyond what their roles require.

Are All 93 ISO 27001 Controls Mandatory?

This is one of the most important things to understand.

No, organizations do not simply have to implement all 93 Annex A controls.

ISO 27001 follows a risk-based approach. An organization identifies its information security risks, determines how those risks should be treated, and selects appropriate controls. Annex A acts as a reference set to help organizations ensure that relevant control areas have been considered.

This is where the Statement of Applicability (SoA) becomes important. It records which controls are applicable, whether they are implemented, and the justification for including or excluding them.

For example, a company operating entirely through cloud infrastructure may face very different physical security risks from an organization that owns and operates its own data center.

The key is not to implement controls simply because they appear on a list. The goal is to implement controls that are appropriate to the organization’s risks and context.

A Quick ISO 27001 Controls Checklist

Before moving toward certification, organizations should be able to answer questions such as:

1. Have we identified and assessed our information security risks?

2.Have we determined how those risks will be treated?

3. Have we identified which Annex A controls are applicable?

4. Is our Statement of Applicability documented?

5. Are the relevant controls actually implemented?

6. Are employees aware of their security responsibilities?

7. Are access rights reviewed and removed when no longer required?

8. Are vulnerabilities identified, assessed, and addressed?

9. Do we have an incident response process?

10. Are important suppliers and third parties assessed for security risks?

This checklist is not a substitute for the ISO 27001 standard or a formal audit, but it provides a useful starting point for identifying readiness gaps.

Common Gaps in ISO 27001 Implementation

Organizations can struggle with ISO 27001 when controls exist on paper but are not consistently implemented.

Common gaps include:

  • Employees having unnecessary access to sensitive systems
  • Incomplete access reviews
  • Outdated security policies
  • Inconsistent vulnerability management
  • Missing or incomplete security logs
  • Unclear incident response responsibilities
  • Inadequate supplier security assessments
  • Lack of evidence showing that controls are operating

The important lesson is simple: having a security policy is not the same as having an effective security control.

Controls need to be implemented, monitored, reviewed, and supported by appropriate evidence.

How Greyhound Can Help?

Strengthening ISO 27001 readiness requires visibility into the technical security risks within your environment.

Greyhound can help organizations with the technical side of their security and certification readiness through automated security scans, black-box penetration testing, evidence collection, and security posture assessment. By identifying vulnerabilities, misconfigurations, and other technical security gaps, Greyhound helps teams understand where their existing security measures need attention. The resulting assessment and testing evidence can also support an organization’s broader ISO 27001 implementation and certification efforts.

Conclusion

Understanding ISO 27001 controls does not mean trying to memorize 93 controls. It means understanding your organization’s information security risks and putting appropriate safeguards in place to manage them.

From organizational policies and employee awareness to physical protection and technological security, the four control categories work together to create a more complete information security program.

The real goal is not to check every box on a list. It is to know your risks, choose the right controls, implement them consistently, and maintain evidence that they are working.

That is what turns ISO 27001 from a certification exercise into an ongoing approach to protecting information and building trust.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *