Implementing information security pragmatically according to ISO 27001 and BSI
How to build an ISMS with integrated risk analysis, prepared measures and audit-ready reporting.
Next date: 8 December 2026, 01:00View datesThe standard defines what an information security management system has to deliver. In the audit, what counts is that you can prove it. CRISAM® brings scope, risks, controls, measures and evidence together in one shared model, from assessment through justification and implementation to the report.
As of: 23 September 2026
| Nonconformity | Reference | Rating | Status |
|---|---|---|---|
| Statement of Applicability not up to date | Clause 6.1.3 | open | |
| Effectiveness of measures not evaluated | Clause 9.1 | in progress | |
| Supplier requirements incomplete | Annex A | in progress | |
| Management review documented | Clause 9.3 | done |
ISO/IEC 27001 is the international standard for information security management systems. It defines how an ISMS is established, operated and continually improved: define the scope, assess risks, select and justify measures, check effectiveness. Certification is voluntary and is granted by accredited certification bodies.
The current version is the third edition, ISO/IEC 27001:2022, supplemented by Amendment 1:2024 on climate action. The German version was published as DIN EN ISO/IEC 27001:2024-01, the amendment as DIN EN ISO/IEC 27001/A1:2024-11.
Under ISO/IEC 17021-1, management system certification runs in a three-year cycle. The ISMS must also be demonstrably kept in operation between audits.
The certification body reviews scope, documentation and maturity. The result shows whether the ISMS is ready for audit.
Implementation is audited on site: risk assessment, Statement of Applicability, effectiveness of measures. The certification decision follows.
It takes place in the first year after certification. The focus is on internal audits, management review, nonconformities and corrective actions.
It takes place in the second year. The audit checks whether risks have been reassessed and whether the previous year's measures are effective.
In the third year, the entire management system is audited again before the certificate expires.
After recertification, the cycle starts again. Certificates issued under the previous edition, ISO/IEC 27001:2013, have no longer been valid since the transition period ended on 31 October 2025. The transition period is defined in IAF MD 26.
The certificate is not required by law. It is demanded by customers, clients and the entities whose supply chain you are part of.
The standard does not require evidence for the entire company. What gets certified is the scope that you define and justify yourself: sites, organizational units, processes, systems. It determines effort, audit duration and the informative value of the certificate alike.
For each Annex A control, you record whether it is applicable, for what reason and how it has been implemented. The Statement of Applicability, SoA for short, is usually the first document auditors look at in the audit. It links risk treatment and implementation.
In addition to certification to ISO/IEC 27001, there is ISO 27001 certification based on IT-Grundschutz. The certificate is issued by the German Federal Office for Information Security (BSI), and the audit is carried out by BSI-certified auditors.
Clauses 4 to 10 contain the requirements for the management system. Annex A lists the controls. You select from them and justify your selection.
| Requirement | Clause | What is required | How you map it in CRISAM® |
|---|---|---|---|
| Context and scope | Clause 4 | Determine internal and external issues, identify the expectations of interested parties, define and document the scope of the ISMS | Corporate structures, organizational units and assets are mapped and linked to each other. This creates a transparent basis for security and risk analyses. |
| Leadership and security policy | Clause 5 | Top management is accountable for the ISMS, establishes the information security policy and assigns roles, responsibilities and authorities | Approvals, responsibilities and deadlines are stored on the object. KPI-based management reports provide the basis for decisions by top management. |
| Risk assessment and risk treatment | Clause 6 | A repeatable process for assessing information security risks, the selection of treatment options and a risk treatment plan with objectives | Security risks are assessed qualitatively and quantitatively, monitored and treated. The results form the basis for well-founded security measure plans. |
| Statement of Applicability and controls | Clause 6.1.3, Annex A | For each Annex A control, you must record whether it is necessary, why it was included or excluded and whether it is implemented | The integrated ISMS Knowledge Pack provides over 230 building blocks and more than 2,500 control objectives, based on ISO/IEC 27001 and 27002, BSI IT-Grundschutz, ITIL and NIST, among others. Selection, justification and implementation status are documented per control in the same model. |
| Competence and documented information | Clause 7 | Provide resources, ensure competence, create awareness, define communication and control documented information | Evidence, responsibilities and deadlines are linked directly to the respective requirement. The documentation is ready for audit and certification. |
| Operation | Clause 8 | Carry out and control the planned processes, repeat risk assessments at planned intervals and when significant changes occur, implement the risk treatment plan | Measures are planned with workflow support, assigned to owners and monitored during implementation. Regular content updates keep the assessments state of the art. |
| Monitoring, internal audit, management review | Clause 9 | Monitor and measure effectiveness, conduct internal audits at planned intervals, have top management review the ISMS | Benchmarking and compliance assessments compare the ISMS with international standards. Standardized reports are available for audits, certifications and external reviews. |
| Nonconformity and improvement | Clause 10 | Address nonconformities, eliminate causes, document corrective actions and continually improve the ISMS | Nonconformities and weaknesses are identified systematically. Improvement measures can be created, assigned to owners and monitored with workflow support. |
From the scope to the documents for the certification audit.
The wizard guides you through delimiting sites, units, processes and systems and documents what is excluded and why. The scope defined this way later appears on the certificate.
The standard does not prescribe it. You define it and justify it. It later appears on the certificate.
ExclusionsEvery exclusion needs a justification that holds up in the audit. Interfaces to the excluded area must still be considered.
ChangesIf the scope grows, the risk situation changes. The assessment is then triggered again.
The requirements catalog compares every clause of the standard with the current state. This shows you where gaps exist: for which requirement, in which clause and how serious.
| Requirement | Clause | Actual | Target | Severity |
|---|---|---|---|---|
| Monitor and measure effectiveness | 9.1 | 1 | 4 | |
| Keep Statement of Applicability up to date | 6.1.3 | 2 | 4 | |
| Internal audit program | 9.2 | 2 | 4 | |
| Manage supplier relationships | Annex A | 2 | 4 | |
| Provide evidence of awareness and training | 7.3 | 3 | 4 |
The risk assessment starts with the assets in scope. Each risk is assigned a treatment option and the controls intended to reduce it.
| Risk | Protection goal | Inherent | Residual | Treatment | Controls |
|---|---|---|---|---|---|
| Outage of the customer platform | Availability | mitigate | Annex A | ||
| Customer data leakage via an interface | Confidentiality | mitigate | Annex A | ||
| Tampering with log data | Integrity | mitigate | Annex A | ||
| Outage of a cloud service provider | Availability | share | Annex A | ||
| Operating error in administration | Integrity | mitigate | Annex A | ||
| Loss of mobile devices | Confidentiality | accept | Annex A |
The Statement of Applicability is generated directly from the answered control objective questions, not as a separate list. For each control, it records whether it is applicable and why.
| Building block | Control objective | Applicable | Justification | Implementation |
|---|---|---|---|---|
| Access control | Access rights assigned by task | yes | Risk treatment | |
| Cryptography | Encryption of data at rest | yes | Customer requirement | |
| Supplier relationships | Security requirements in the contract | yes | Risk treatment | |
| Logging | Protection of log data | yes | Risk treatment | |
| Physical security | Physical access to data centers | no | Operated by the service provider | |
| Development | Secure development environment | yes | Risk treatment | |
| People | Awareness and training | yes | Standard requirement |
| Building block | Open item | Owner |
|---|---|---|
| Supplier relationships | Justification missing for two service providers without a contract clause | Procurement |
| Mobile devices | Exclusion not documented | IT operations |
For every gap, you create a measure with an owner and a deadline. Progress flows back into the same analysis in which the gap became visible.
The result is a report that shows what the standard requires, what has been implemented and what is still open. On the same basis, you prepare the internal audit, management review and certification audit.
| Evidence | Reference | As of | Owner | Status |
|---|---|---|---|---|
| Scope with justification of exclusions | Clause 4.3 | 04.09.2026 | ISMS team | |
| Information security policy with approval | Clause 5.2 | 12.02.2026 | Management | |
| Risk assessment and risk treatment plan | Clause 6.1 | 30.06.2026 | Risk management | |
| Statement of Applicability | Clause 6.1.3 | under revision | ISMS team | |
| Internal audit report | Clause 9.2 | 18.08.2026 | Internal audit | |
| Management review minutes | Clause 9.3 | planned 03/2027 | Management |
Security policy, resources, management review, approval of the scope.
Risk assessment, Statement of Applicability, implementation of controls.
Audit program, internal audits, follow-up of nonconformities.
Supplier requirements, evidence, implementation in day-to-day business.
An information security management system in line with ISO/IEC 27001 covers many requirements that NIS2 and DORA also impose. CRISAM® handles overlapping requirements by mapping the control objective questions to the individual standards.
One answered control objective question applies to ISO/IEC 27001, BSI IT-Grundschutz and NIS2 at the same time.
The integrated ISMS Knowledge Pack provides over 230 building blocks, based on ISO/IEC 27001 and 27002, BSI IT-Grundschutz, ITIL and NIST, among others.
CRISAM® complements your existing systems and connects them via interfaces.
CRISAM® ISMS Classic is integrated with data protection, Business Continuity Management and Enterprise Risk Management. The result is one consistent management system instead of isolated solutions for each topic.
In Germany, there are two paths to a certificate under ISO/IEC 27001. The first goes through an accredited certification body that audits against the standard. The second goes through IT-Grundschutz: the audit is based on BSI Standards 200-1, 200-2 and 200-3 and the IT-Grundschutz Compendium, it is performed by a BSI-certified auditor, and the certificate is issued by the German Federal Office for Information Security (BSI).
| Criterion | ISO/IEC 27001 | ISO 27001 based on IT-Grundschutz |
|---|---|---|
| Basis | The standard ISO/IEC 27001:2022, German version DIN EN ISO/IEC 27001:2024-01 | The same standard, supplemented by BSI Standards 200-1, 200-2 and 200-3 and the IT-Grundschutz Compendium |
| Approach | The standard does not prescribe a method. You define risk assessment, selection and justification of controls yourself | Three predefined approaches: Basic Protection, Core Protection and Standard Protection |
| Who audits | Auditors of an accredited certification body | BSI-certified auditors |
| Who issues the certificate | The accredited certification body | The German Federal Office for Information Security (BSI), after reviewing the audit report |
| Depth of evidence | The extent results from the scope and the risk assessment | The extent additionally results from the building blocks of the IT-Grundschutz Compendium for the information domain |
| Statement of Applicability | Mandatory document under Clause 6.1.3 of the standard | Mandatory document under Clause 6.1.3 of the standard, plus the IT-Grundschutz documentation |
| Mapping in CRISAM® | Building blocks and control objectives of the ISMS Knowledge Pack, mapped to the clauses of the standard | The same control objective questions, additionally mapped to BSI IT-Grundschutz |
Which path is the right one depends on who requires the evidence. If you also have to meet legal requirements, keep in mind: a certified ISMS replaces neither the registration nor the reporting obligations under NIS2 or DORA, but it covers many of the areas of measures required there. An overview of all frameworks covered by CRISAM® is available under Standards and frameworks.
A webinar on the approach and a case study from the field.
How to build an ISMS with integrated risk analysis, prepared measures and audit-ready reporting.
Next date: 8 December 2026, 01:00View dates
How an IT consulting firm maps its information security management system in CRISAM®.
Read the case studyWebinars and training sessions at a glance, plus the self-paced courses of the CRISAM® Academy and the product documents in the download center.
AcademyDownload centerThe first step depends on where you stand today.
You start with the initial modeling: corporate structure, organizational units and assets. The ISMS Knowledge Pack provides the building blocks and control objectives for the assessment, so you do not have to create the catalog yourself.
It starts with the gap analysis. Existing answers are carried over and assessed. You see which requirements are open, who is responsible for them and by when they should be implemented.
What matters is that the surveillance audit and recertification build on the same basis as day-to-day operations. Nonconformities, corrective actions and evidence are available as a report.
For this you need the CRISAM® GRC Platform, the CRISAM® ISMS Module and the ISMS 27001 Knowledge Pack. In the demo, we discuss your starting point and show what you already have in place.
ISO/IEC 27001 is the international standard for information security management systems. It defines how an ISMS is established, operated and continually improved: define the scope, assess risks, select and justify measures, check effectiveness. Certification is voluntary and is granted by accredited certification bodies.
The current version is the third edition, ISO/IEC 27001:2022, supplemented by Amendment 1:2024 on climate action. The German version was published as DIN EN ISO/IEC 27001:2024-01, the amendment as DIN EN ISO/IEC 27001/A1:2024-11. Certificates issued under the previous edition, ISO/IEC 27001:2013, have no longer been valid since the transition period ended on 31 October 2025. The transition period is defined in IAF MD 26.
In Germany, there are two paths to a certificate under ISO/IEC 27001. The first goes through an accredited certification body that audits against the standard. The second goes through IT-Grundschutz: the audit is based on BSI Standards 200-1, 200-2 and 200-3 and the IT-Grundschutz Compendium, it is performed by a BSI-certified auditor, and the certificate is issued by the German Federal Office for Information Security (BSI).
Clauses 4 to 10 of the standard contain the requirements for the management system: context and scope, leadership and security policy, planning with risk assessment and risk treatment, support with competence and documented information, operation, performance evaluation with internal audit and management review, and improvement. Annex A lists the controls you select from. You record the selection and its justification in the Statement of Applicability.
Under ISO/IEC 17021-1, management system certification runs in a three-year cycle. The two-stage certification audit is followed by surveillance audits in the first and second year and by recertification in the third year. After that, the cycle starts again. The ISMS must also be demonstrably kept in operation between audits, for example through internal audits, management review and corrective actions.
CRISAM® handles overlapping requirements by mapping the control objective questions to the individual standards. The integrated ISMS Knowledge Pack provides over 230 building blocks and more than 2,500 control objectives, based on ISO/IEC 27001 and 27002, BSI IT-Grundschutz, ITIL and NIST, among others. One answered control objective question therefore applies to several frameworks and does not have to be collected again for each standard.
At the latest when several people work on the ISMS and evidence has to remain audit-ready over several years. Spreadsheets lack the link between risk, control, measure and evidence, and every analysis has to be compiled from scratch. In CRISAM®, these elements are linked in one model. Nonconformities and weaknesses are identified systematically, and improvement measures can be created, assigned to owners and monitored with workflow support.
The same data set the ISMS runs on in day-to-day operations. CRISAM® delivers standardized reports for audits, certifications and external reviews as well as export functions for stakeholders and customers. Benchmarking and compliance assessments reveal deviations and nonconformities before the auditor finds them.
The information on the standard and on certification on this page comes from the following sources.
The information reflects the status of the sources cited as of the review date stated above.
In the demo, we walk through your case together: scope, gap analysis, risk assessment, Statement of Applicability and the finished report.
You are currently viewing a placeholder content from Facebook. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Embedded Content. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from HubSpot. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from Instagram. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More InformationYou are currently viewing a placeholder content from X. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
More Information