How to prepare for certification?
The short answer
ISO 27001 does not tell an organization exactly which security tools to buy. It requires the organization to build a management system that identifies its information security risks, chooses controls to treat them, operates those controls, measures whether they work, and improves continuously. Certification confirms, through an independent audit, that this system exists and is functioning.
The essential idea is that ISO 27001 is a management standard. It is less about achieving a perfect security posture and more about proving that security is governed: risks are known, decisions are documented, controls are operated, and the organization learns from what goes wrong.
Why companies pursue ISO 27001
The motivations usually fall into a few groups. The most common is commercial: certification shortens security reviews in sales cycles and opens doors with enterprise customers who require it from their suppliers. Another is contractual and regulatory: in regulated industries and their supply chains, ISO 27001 is often the reference framework used to demonstrate adequate security, and it supports compliance with data protection laws such as the LGPD by providing a structured way to show that appropriate technical and organizational measures are in place.
There is also an internal motivation that is often underestimated. Preparing for certification forces an organization to know its assets, assign owners, assess risks consistently, and define responsibilities. Many leaders report that this clarity is as valuable as the certificate itself.
How the standard is structured
The current version of the standard is ISO/IEC 27001:2022. The transition period from the previous 2013 version has ended, so organizations certifying today work with the 2022 version. Its requirements are organized into clauses 4 to 10, which follow the Plan, Do, Check, Act logic common to ISO management system standards:
- Clause 4, Context of the organization: understanding internal and external issues, interested parties, and defining the scope of the ISMS.
- Clause 5, Leadership: top management commitment, the information security policy, and assigned roles and responsibilities.
- Clause 6, Planning: the risk assessment and risk treatment processes, and information security objectives.
- Clause 7, Support: resources, competence, awareness, communication, and documented information.
- Clause 8, Operation: carrying out the risk assessment and treatment and operating the planned controls.
- Clause 9, Performance evaluation: monitoring and measurement, internal audit, and management review.
- Clause 10, Improvement: handling nonconformities, corrective action, and continual improvement.
All of these clauses are mandatory for certification. They describe how the management system must work, regardless of the organization’s size or sector.
The Annex A controls
Alongside the clauses, Annex A lists a reference set of 93 information security controls organized into four themes. Organizations do not have to implement every control. They must consider each one against the results of their risk assessment, decide whether it applies, and justify the decision.
| Theme | Number of controls | Examples of what it covers |
|---|---|---|
| Organizational | 37 | Policies, roles, asset management, supplier relationships, threat intelligence, incident management |
| People | 8 | Screening, terms of employment, awareness and training, remote working |
| Physical | 14 | Secure areas, equipment protection, physical security monitoring |
| Technological | 34 | Access control, secure configuration, logging and monitoring, vulnerability management, secure development |
A companion standard, ISO/IEC 27002, provides detailed guidance on how each control can be implemented. It is not certifiable, but it is the most useful reference when designing controls in practice.
The steps to certification
While every project adapts to the organization, the path to certification follows a well-established sequence.
- Define the scope. Decide which parts of the organization, locations, processes, and systems the ISMS will cover. A well-chosen scope keeps the project manageable without excluding what customers actually care about.
- Perform a gap analysis. Compare current practices with the requirements of the standard to understand how much work lies ahead.
- Build the asset inventory. Identify the information assets in scope and assign an owner to each. A reliable asset inventory is the foundation of every later step.
- Assess and treat risks. Apply a consistent methodology to identify risks to those assets, evaluate them, and decide how each will be treated.
- Prepare the Statement of Applicability. Document which Annex A controls apply, which do not, the justification for each decision, and the implementation status.
- Implement controls and policies. Put the selected controls into operation, write the required policies and procedures, and train people.
- Operate and collect evidence. Run the ISMS for a period long enough to generate records showing that controls work in practice.
- Conduct an internal audit and management review. Check the system independently from within and have top management review its performance.
- Undergo the certification audit. An accredited certification body performs the audit in two stages. Stage 1 reviews the documentation and readiness. Stage 2 verifies that the ISMS is implemented and effective.
The time required depends heavily on the organization’s size, scope, and starting maturity, ranging from a few months for small, well-organized companies to a year or more for complex environments.
Evidence: where security operations meet compliance
The most common surprise in a first certification is how much the audit depends on evidence that security actually operates. Policies alone are not enough. Auditors look for proof: records of access reviews, logs showing that monitoring takes place, results of vulnerability assessments, and records of how incidents were handled.
This is where security operations and compliance become the same work. Regular penetration testing provides evidence for technical vulnerability management and for testing the effectiveness of controls. Continuous monitoring, whether internal or delivered through a managed SOC, provides evidence for logging, monitoring, and incident management. An organization whose security operations already run continuously finds that much of the evidence the auditor requests already exists.
After certification: keeping it alive
An ISO 27001 certificate is valid for three years, but it is not a one-time achievement. The certification body conducts surveillance audits in the first and second years to confirm that the ISMS is still operating, followed by a recertification audit at the end of the cycle. Between audits, the organization is expected to keep assessing risks, operating controls, running internal audits, and acting on nonconformities.
Organizations that treat certification as a finish line usually struggle at the first surveillance audit, because evidence stops being produced once the project team disbands. The ones that succeed treat the ISMS as part of normal operations.
Common mistakes on the way to certification
Several mistakes appear repeatedly in ISO 27001 projects:
- Treating it as a documentation project. Writing policies without operating the corresponding controls leads to findings in Stage 2.
- Choosing the wrong scope. A scope that is too broad stalls the project, while one that is too narrow may not satisfy the customers who requested certification.
- Copying generic templates. Documents that do not reflect how the organization really works are easy for an auditor to identify.
- Underestimating evidence collection. Gathering proof manually from many systems consumes far more time than expected. Compliance automation platforms that connect to the organization’s systems and collect evidence continuously reduce this burden significantly.
- Leaving leadership out. The standard explicitly requires top management involvement, and auditors check it.
- Forgetting suppliers. Supplier relationships are part of Annex A, and many organizations discover late that they have no structured way to assess them.
How Mercurius supports ISO 27001 projects
Mercurius supports ISO 27001 projects by combining consultancy with operational security. The consultancy side covers scoping, gap analysis, risk assessment, the Statement of Applicability, and preparation for the audits, supported by compliance automation that keeps controls and evidence monitored continuously instead of assembled at the last minute.
The operational side is what makes the difference in the audit. Because Mercurius also runs penetration testing, threat intelligence, and an AI-native managed SOC, many technological controls are not only documented but actually operated, producing the evidence auditors look for as a natural result of day-to-day security. The goal is a certification that reflects real security, and an ISMS that stays healthy after the certificate is issued.
Frequently asked questions
What is the difference between ISO 27001 and ISO 27002?
ISO 27001 defines the requirements for an information security management system and is the standard organizations are certified against. ISO 27002 provides detailed guidance on implementing the security controls listed in Annex A. It is a reference document and cannot be certified on its own.
Do we need to implement all 93 Annex A controls?
No. Each control must be considered against the organization’s risk assessment. Controls that do not apply can be excluded, provided the decision is justified in the Statement of Applicability.
How long does ISO 27001 certification take?
It depends on the scope, size, and starting maturity of the organization. Small, well-organized companies can be ready in a few months, while complex environments may need a year or more. The ISMS must also operate for a period before the audit so that evidence exists.
How long is an ISO 27001 certificate valid?
Three years, with surveillance audits in the first and second years and a recertification audit at the end of the cycle. The ISMS must be maintained and improved continuously during this period.
Does ISO 27001 help with LGPD compliance?
Yes. ISO 27001 does not replace the specific obligations of data protection laws, but it provides a structured way to demonstrate that appropriate technical and organizational security measures are in place, which supports LGPD compliance.



