# ISMS Governance Policy

> **Document control**  
> Owner: [POLICY_OWNER_ROLE, e.g. Information Security Officer]  
> Approved by: [APPROVER_NAME_AND_ROLE]  
> Version: [VERSION]  
> Effective date: [EFFECTIVE_DATE]  
> Next review: [NEXT_REVIEW_DATE]

## 1. Legal/Regulatory Basis

ISO/IEC 27001:2022 / ISO/IEC 27002:2022, Annex A:

- A 5.1: Policies for Information Security
- A 5.2: Information Security Roles and Responsibilities
- A 5.3: Segregation of Duties
- A 5.4: Management Responsibilities
- A 5.9: Inventory of Information and Associated Assets
- A 5.11: Return of Assets
- A 5.31: Legal, Statutory, Regulatory and Contractual Requirements
- A 5.34: Privacy and Protection of PII
- A 5.35: Independent Review of Information Security
- A 5.36: Compliance with Policies, Rules and Standards for Information Security
- A 5.37: Documented Operating Procedures

BSI IT-Grundschutz:

- ISMS.1.A3 (Information Security Policy)
- ORP.1.A1 (Responsibilities and Regulations)
- ISMS.1.A11 (Maintaining Information Security)
- DER.3.1 (Audits and Revisions)
- OPS.1.1.1.A3 (Operational Handbooks)
- OPS.1.1.1.A7 (Orderly IT Operations)

Additional jurisdiction-specific laws and regulations, in particular records retention law (e.g. German HGB §257, tax code §147) and data protection law, are listed in the Legal Register and incorporated by reference.

## 2. Purpose & Scope

This policy establishes the framework for creating, approving, distributing, reviewing and maintaining all documented information within the Information Security Management System (ISMS) of **[YOUR_ORGANISATION_NAME]**. It ensures that policies, procedures, records and other documented information are controlled, current, accessible and traceable. It also governs information security roles and responsibilities, segregation of duties and management responsibilities, the inventory of information and associated assets and their return, the handling of legal, statutory, regulatory and contractual requirements, the independent review of information security and the link to privacy and the protection of PII.

The policy applies to all ISMS documentation. The document hierarchy consists of the Information Security Policy and the Risk Management Policy at the top, followed by topic-specific policies covering individual security domains, supporting management documents (Asset Management, Corrective Actions & Improvement Register, Information Security Objectives, Stakeholder Register, Communication Plan, Internal Audit Programme, Audit Schedule) and operational records generated by day-to-day processes. All personnel responsible for creating, reviewing, approving or maintaining ISMS documentation are bound by this policy.

## 3. Information Security Policies (A 5.1)

The information security policy and all topic-specific policies are defined, approved by management, published, communicated to relevant personnel and interested parties, acknowledged by recipients, and reviewed at planned intervals and when significant changes occur. The policy framework is structured as a document hierarchy with clear ownership, approval authority and review responsibilities at each level.

### 3.1 Policy Considerations

The information security policy takes into consideration the following inputs:

- **Business Strategy & Requirements:** The information security policy reflects the current business strategy, operational objectives and commercial requirements. Security controls are aligned with business priorities and resource constraints.
- **Regulations, Legislation & Contracts:** The policy incorporates all applicable regulatory, statutory, legislative and contractual requirements. A legal register is maintained and referenced to ensure ongoing compliance.
- **Current & Projected Risks:** The policy accounts for both current information security risks identified through risk assessment and projected threats derived from threat intelligence and industry trend analysis.

### 3.2 Policy Content Requirements

The information security policy contains the following elements:

- **Definition of Information Security:** The policy provides a clear, organisation-specific definition of information security encompassing the protection of confidentiality, integrity and availability of information assets.
- **Objectives Framework:** The policy establishes a framework for setting measurable information security objectives that are reviewed annually and aligned with the risk assessment results.
- **Guiding Principles:** Core principles are stated that guide all information security activities: risk-based decision making, defence in depth, least privilege, separation of duties and continual improvement.
- **Commitment to Requirements:** The policy includes an explicit commitment to satisfy all applicable legal, regulatory, contractual and self-imposed requirements related to information security.
- **Commitment to Continual Improvement:** The policy includes a commitment to the continual improvement of the ISMS through the Plan-Do-Check-Act cycle.
- **Role Assignments:** Responsibilities for information security management are assigned to defined roles. The RACI matrix documents accountability, responsibility, consultation and information flows for each ISMS activity.
- **Exemptions & Exceptions:** A formal exemption request process is provided. Each exemption request captures the affected policy or control, justification, risk analysis, compensating controls and expiry date. The relevant risk owner is consulted for input, but the Information Security Officer is the sole formal approver to ensure a single accountable decision point. Exemptions are monitored during their validity and closed at expiry or earlier.

### 3.3 Document Hierarchy & Topic-Specific Policies

The Information Security Policy is supported by topic-specific policies that provide detailed requirements for each security domain. Several related domains are addressed in consolidated policies: incident management, technical vulnerabilities, change management and supplier reviews are covered by the Security Operations Policy; backup, networking, logging, monitoring and operational IT are combined in the IT Operations Policy. Asset management is documented in an Asset Management register rather than as a dedicated topic-specific policy. The following topics are in scope of the policy framework:

- Access control
- Physical and environmental security
- Asset management
- Information transfer
- Secure configuration and handling of user endpoint devices
- Networking security
- Information security incident management
- Backup
- Cryptography and key management
- Information classification and handling
- Management of technical vulnerabilities
- Secure development

Additional topic-specific policies cover human resource security, remote working, supplier security, business continuity, secure project management, data protection, intellectual property, configuration management and risk management. Each topic-specific policy references the applicable ISO 27001 Annex A controls and BSI IT-Grundschutz Bausteine.

### 3.4 Approval & Authorisation

- **Information Security Policy:** The overarching information security policy and any amendments to it are approved by top management before publication; an amendment takes effect only with that approval. The amended text is released as a new version and the previous version is retained as a record.
- **Topic-Specific Policies:** Each topic-specific policy is approved by the appropriate level of management with the authority and technical competency for the respective domain. The approver is documented in the policy metadata.

### 3.5 Review & Update

Policies are reviewed at least annually and additionally when triggered by specific events. Review responsibility is allocated to personnel with the appropriate authority and technical competency for the policy domain.

Review triggers:

- **Business Strategy Changes:** When the organisation's business strategy, objectives or operating model change significantly.
- **Technical Environment Changes:** When new technologies, platforms or architectures are introduced or existing systems undergo major changes.
- **Regulatory Changes:** When applicable laws, regulations, statutes or contractual obligations change.
- **Risk Landscape Changes:** When new information security risks are identified or the severity of existing risks changes materially.
- **Threat Environment Changes:** When the threat landscape evolves, including emerging attack techniques, new threat actors or sector-specific advisories.
- **Lessons Learned:** When information security events or incidents reveal gaps in policy coverage or effectiveness.

Review inputs:

- **Management Review Outputs:** Decisions and action items from management reviews that affect policy content or scope.
- **Audit Findings:** Internal and external audit results that identify policy gaps, ambiguities or non-compliance.
- **Related Policy Updates:** Changes to other policies within the ISMS that create dependencies or conflicts with the policy under review.

### 3.6 Communication & Acknowledgement

Policies are communicated to all relevant personnel and interested parties in a form that is accessible and understandable to the intended audience. Recipients are required to acknowledge that they have read, understood and agree to comply with the applicable policies. The following communication methods are used:

- **Digital Distribution & Acknowledgement:** Policies are distributed electronically and signed using a policy acknowledgement mechanism with auditable evidence (e.g. eIDAS-compliant signatures with one-time-password verification, document hash and audit trail). Signed acknowledgements are persisted as policy acknowledgement records and linked to the onboarding process so that every new employee acknowledges the applicable policies during onboarding.
- **Briefings & Meetings:** Key policy changes are communicated in team meetings, onboarding sessions and annual awareness briefings. Attendance records serve as acknowledgement evidence for meeting-based communication.

## 4. Information Security Roles & Responsibilities (A 5.2)

All information security roles and responsibilities are assigned in writing, documented and communicated. Each security area for which individuals are responsible is clearly defined, and the associated authorisation levels are set out. Individuals taking on an information security role have the necessary competence and keep their knowledge current through continual professional education. Security tasks may be delegated, but accountability remains with the originally named role. All relevant tasks and functions are clearly defined and demarcated, and changes to the organisational structure are communicated to all employees in a timely manner. For all essential functions in the security organisation, effective deputy arrangements are in place so that security work continues without interruption when key personnel are unavailable.

### 4.1 Assignment of Responsibilities

The following areas have named accountability:

- **Protection of Information and Associated Assets:** Responsibility for protecting individual information assets and other associated assets is assigned to named asset owners. Asset owners are responsible for classification, defining access entitlements and the continuing adequacy of protection measures for their assets.
- **Execution of Security-Specific Processes:** Responsibility for executing specific information security processes (e.g. access management, vulnerability handling, incident response, change management, backup) is unambiguously assigned to individual roles and documented in the RACI matrix.
- **Risk Management & Residual Risk Acceptance:** Risk assessments are performed by the ISO in collaboration with the respective risk owners. Formal acceptance of residual risk rests solely with the named risk owner for the affected area and is recorded in the risk register.
- **All Users of Information and Associated Assets:** Every employee and contractor who uses organisation-owned information or associated assets is responsible for handling them in line with their classification and applicable policies. This responsibility forms part of the employment contract and is communicated during onboarding.
- **Overall Responsibility for Information Security:** Overall responsibility for the development, implementation and maintenance of information security rests with the Information Security Officer (ISO) formally appointed by top management. The ISO is provided with adequate resources, reports directly to top management and is involved early in all major projects and the introduction of new applications and IT systems. Where the ISO role is filled by an external person, the contract additionally covers a confidentiality undertaking and a controlled handover at contract end.
- **Delegation without handing over accountability:** Security tasks may be delegated to suitable persons; accountability stays with the role the task is assigned to. Whoever delegates a task verifies that it was actually and correctly done and records the result.
- **Scope and competence per security area:** Every security area has a written scope and a defined authorization level. The person holding the role has the competence it requires, keeps it current through the training plan and is reassigned when the role changes.

The concrete assignment of Responsible, Accountable, Consulted and Informed for each ISMS activity is maintained in the RACI matrix. The RACI matrix is reviewed annually and updated after organisational changes, role changes or the introduction of new security processes. Responsibility for the security of every business process, application, IT system, location and communication link is assigned, and all employees are informed about the tasks they hold. The adequacy of the security organisation structure is reviewed in the annual management review cycle.

## 5. Segregation of Duties (A 5.3)

Conflicting duties and areas of responsibility are distributed among different individuals in such a way that no single person can carry out, approve and verify a security-critical activity alone. Segregation reduces the risk of deliberate manipulation, accidental errors and misuse of privileges. Where full segregation is not feasible due to organisation size, compensating controls such as enhanced logging, activity monitoring and stronger management oversight are put in place, and the justification is recorded in the exemption register.

### 5.1 Segregated Activity Areas

The following activities require segregation of duties:

- **Change Management:** The initiation, approval and execution of a change are not performed by the same person. The requester, approver and implementer are distinct roles within the change management workflow.
- **Access Rights Management:** Requesting, approving and technically provisioning access rights are distributed across different roles. Line managers or asset owners approve access, IT provisions it technically, and the ISO verifies samples through access reviews.
- **Software Development & Code Review:** Development, code review and merge approval are performed by different individuals. A developer who writes code does not approve its own integration into the production branch.
- **Development vs. Production Operations:** Developers do not have administrative access to production systems. Administration of the production environment is handled by a separate role (Operations/Platform team). Read access for troubleshooting is only granted on justified request and on a need-to-know basis.
- **Application Use vs. Administration:** Users who consume an application in daily business do not hold administrative rights on the same application. Administrative tasks are performed via dedicated admin accounts separate from personal user accounts.
- **Application Use vs. Database Administration:** Administration of production databases is not performed by the functional users of the associated application. Database administrators are a separate role, and direct database manipulations are monitored and logged.
- **Control Design vs. Audit:** The design and operation of information security controls is segregated from their independent review. Individuals who design or operate a control do not conduct the internal audit of that control; this is performed by the internal audit function or an external party (see A 5.35).
- **Compensating controls where duties cannot be separated:** Where the size of the organisation does not allow duties to be spread across different people, a compensating control replaces the separation: four-eyes approval, subsequent review by a second person or logging with evaluation. Processes are designed from the outset so that two people would have to collude to bypass a control.

When designing segregation of duties, the possibility of collusion is considered, in particular in small teams. Conflicting operational and controlling functions are distributed among different individuals; deputy arrangements are subject to the same segregation. Segregation is enforced technically through the identity and access management system, ensuring that conflicting permissions are not assigned to the same user account simultaneously. Where full segregation is not practicable, compensating controls are in place: enhanced logging of security-critical operations, independent log review by the ISO, additional management oversight and rotation of sensitive activities where feasible. Any deviation from segregation of duties is justified, accompanied by compensating controls and recorded via the Exemption Request workflow.

## 6. Management Responsibilities (A 5.4)

Top management and all line managers require employees and contractors to comply with the information security policy and all topic-specific policies in accordance with their established roles and responsibilities. Management actively supports the ISMS, provides the necessary resources and takes responsibility for ensuring that information security is lived in day-to-day operations. Top management assumes overall responsibility for information security visibly to all parties, leads by example and is regularly informed about the status of information security as well as risks and consequences of missing controls. All line managers actively support information security by complying with security requirements themselves and by drawing their employees’ attention to compliance.

### 6.1 Management Duties

Management ensures that all employees and contractors:

- **Briefing Before Access is Granted:** New employees and contractors are briefed on their information security roles and responsibilities before the first access to information and associated assets is granted. The briefing is part of the onboarding workflow; completion of the training and briefing phase is recorded in the onboarding record and confirmed by the line manager. Mandatory, comprehensible and current guidelines for the use of the relevant components are available to all employees.
- **Role-Specific Security Guidelines:** All employees receive guidelines that describe the information security expectations of their role. These expectations are part of the job description and are updated when roles change.
- **Mandatory Policy Compliance:** Compliance with the information security policy and all topic-specific policies is mandatory for all employees and contractors. This obligation is contractually anchored and documented through policy acknowledgement signatures.
- **Role-Appropriate Security Awareness:** Every employee achieves a level of security awareness appropriate to their role. Baseline training applies to all, and specialised training (e.g. for administrators, developers, HR staff, managers) is assigned depending on the role.
- **Compliance with Employment Terms:** Line managers actively enforce compliance with the terms of employment or engagement, including the information security policy and appropriate methods of working. All employees are obliged to comply with applicable laws, regulations and internal rules; the legal framework of their activity is made known to them, as is the obligation to protect information security outside working hours and outside company premises. Breaches are handled in accordance with the documented disciplinary process of the HR Security Policy; employees are aware of the possible consequences of violating security requirements.
- **Maintenance of Technical Competence:** Employees with information security responsibilities are provided with adequate further education opportunities (training, certifications, industry events) to keep their competence current. Training needs are agreed annually between manager and employee.
- **Confidential Reporting Channel (Whistleblowing):** A confidential channel is available for reporting violations of the information security policy, topic-specific policies or procedures. The channel accepts reports anonymously; where a reporter identifies themselves, their identity is known only to those handling the report. Reports are processed without retaliation against the reporter. Intake, processing path and deadlines are defined; top management, in consultation with the ISO, names the responsible intake point.
- **Resources & Project Time:** Top management provides adequate resources and project planning time for implementing security-related processes and controls. Security requirements are factored into project planning rather than being added as an afterthought.
- **Visible management support:** Top management shows its support for information security through what it does: it provides the resources committed in the risk treatment plan, takes part in the management review, decides on residual risks itself and addresses security topics in internal communication. The signature under the policy alone does not count as support.

## 7. Inventory of Information and Associated Assets (A 5.9)

This policy sets out the requirements for asset management. An inventory of all information and other associated assets is maintained centrally in the asset register; each entry records owner, custodian, classification by confidentiality, integrity and availability, lifecycle status and dependencies to other assets. The inventory covers physical and logical assets (endpoint devices, servers, network components, applications, databases, cloud services, datasets, documents, physical storage media, authentication hardware) and follows a structured recording of business processes, applications, IT systems, rooms, buildings and communication links together with their respective protection needs. The level of detail is aligned with the importance and sensitivity of the asset. Productive components, test instances and reserve components are inventoried alike, as are assets that are no longer in active use until formal disposal. For each asset the owner, location or hosting site, classification, dependencies to supporting components (databases, storage, software components) and lifecycle status are recorded.

### 7.1 Inventory Maintenance & Accuracy

- **Regular Inventory Review:** Asset owners regularly reconcile the inventory with actually present assets. The review cadence is determined by the importance and sensitivity of the asset class and is set organisationally; for productive IT assets the review is performed at least annually, more frequently for highly sensitive assets. The target/actual comparison also covers whether configurations recorded in Asset Management match the actual state. Discrepancies are investigated, corrected and recorded as findings.
- **Inventory Update on Change:** Installing, changing or removing an asset triggers an inventory update. The update is performed by the asset owner in the asset register, driven by the corresponding procurement, onboarding, change and disposal activities. Verification and approval procedures are in place before deploying new equipment and operating means; every inventory change is documented.

### 7.2 Classification & Ownership

Each inventory entry is accompanied by:

- **Classification Inheritance:** Technical assets inherit the classification of the information processed or stored on them, in accordance with the Information Classification & Labelling Policy. An asset carrying multiple types of information takes on the highest classification present.
- **Ownership:** Each identified asset has exactly one named asset owner. The owner is responsible for the proper management of the asset throughout its entire lifecycle.

### 7.3 Asset Owner Responsibilities

For each asset in the inventory, asset owners ensure that:

- **Full Inventory Coverage:** All information and associated assets are inventoried in the asset register. Coverage includes both organisation-owned and third-party-provided assets used within the organisation.
- **Appropriate Protection:** Assets are protected in accordance with their classification through the technical and organisational controls defined in the topic-specific policies.
- **Periodic Classification Review:** The classification of each asset is reviewed annually and additionally on significant changes. Changes in sensitivity or business importance result in reclassification.
- **Linkage of Supporting Components:** Components supporting technology assets (databases, storage, software components, sub-components) are listed in the inventory and linked to the parent asset so that dependencies are visible for risk, change and BCM analysis. Software components are recorded with licence type, intended use and contractual usage period. Network components are additionally referenced via the network documentation, which contains a network plan, the logical network structure as well as zoning and segmentation. For operational technology / process control environments, software and system components, deployed product and protocol versions as well as vendor and regulatory restrictions are recorded; for vehicle fleets, a separate inventory list per vehicle is maintained where this is relevant to the business.
- **Acceptable Use Requirements:** Acceptable use requirements are established for each category of asset (see Acceptable Use Policy, RC510).
- **Access Restrictions Matching Classification:** Access restrictions correspond to the classification of the asset, are effective and are reviewed at least twice a year through the access review workflow.
- **Secure Deletion & Disposal:** Information and associated assets are securely deleted or disposed of at decommissioning in accordance with the Data Deletion, Masking & DLP Policy and removed from the inventory or marked as decommissioned.
- **Risk Involvement of Asset Owners:** Asset owners actively participate in identifying and treating risks affecting their assets and are involved in the risk assessment process.
- **Support for Operational Personnel:** Asset owners support the operational personnel entrusted with day-to-day management of their assets and are available for technical decisions.
- **Depth of the register:** Assets are recorded in the asset register together with their importance to the organisation. The depth of the register follows what the organisation can actually maintain: fewer, well-kept attributes per asset are preferred over many outdated ones.
- **Custody and ownership:** The day-to-day care of an asset may be handed to another person or a service provider; ownership of the asset stays with the responsible person recorded in the asset register.

Asset owner tasks may be delegated operationally (e.g. to IT for technical administration), but formal accountability remains with the named asset owner.

## 8. Return of Assets (A 5.11)

All employees and contractors return any information and associated assets of the organisation in their possession at termination of their employment or contract. The return is part of the formalised offboarding workflow. Assets to be returned are listed per employee in the asset register and are reconciled before the offboarding is closed. The return is handled in a controlled manner: outgoing employees are reminded of existing confidentiality obligations before departure; all affected functions (in particular IT operations, HR and where applicable security personnel) are informed of the departure; emergency and operating plans are updated. To avoid conflicts of interest after a job change, non-compete clauses or cooling-off periods are agreed contractually where required.

### 8.1 Return Obligations

- **Return of All Issued Assets:** All physical and electronic assets previously issued that are owned by or entrusted to the organisation are returned. The offboarding workflow contains a checklist of the assets assigned to the individual; confirmation of complete return is a precondition for closing the offboarding. On personnel changes, all user accounts and permissions that are no longer needed are removed.
- **Purchased or Personal Equipment:** In cases where personnel purchase organisational equipment or use their own equipment for work purposes, all relevant organisation-related information is identified, transferred to the organisation and then securely deleted from the device before departure in accordance with the Physical Security Policy and the Data Deletion, Masking & DLP Policy.
- **Handover of Relevant Knowledge:** Where personnel or other interested parties hold knowledge important to ongoing operations, this knowledge is documented before their departure and handed over to the successor or team. The documentation is part of the offboarding workflow with fields for documentation, successor and ongoing projects. Ideally, the outgoing employee briefs the successor directly; if a direct handover is not possible, a detailed written handover document is produced.
- **Protection Against Unauthorised Copying:** During and after the notice period, the unauthorised copying of relevant information (in particular intellectual property) by personnel under notice of termination is prevented as far as practicable. The line manager decides, in consultation with the ISO, which protective measures to activate based on the sensitivity of the outgoing employee’s tasks. Possible measures include restricting access to sensitive areas, enhanced logging of the affected accounts and the use of DLP controls in line with the Data Deletion & DLP Policy. The decision and its implementation are recorded in the offboarding record.

### 8.2 Assets to Be Returned

Return obligations cover in particular:

- User endpoint devices (laptops, tablets, smartphones)
- Portable storage media (external hard drives, USB sticks, memory cards)
- Specialist equipment (e.g. measurement or test equipment, production hardware, cameras)
- Authentication hardware (mechanical keys, hardware tokens, smartcards, access badges) for information systems, sites and physical archives
- Physical copies of information (printouts, notes, manuals)

For assets that cannot be repossessed by the organisation (e.g. BYOD devices), the organisation restricts organisation-owned information on those assets before departure and ensures secure deletion. The deletion is documented. The same return rules apply to external personnel: work results are handed over in a controlled manner, and access rights issued are returned.

## 9. Legal, Statutory, Regulatory & Contractual Requirements (A 5.31)

All legal, statutory, regulatory and contractual requirements relevant to information security are identified, documented and kept current. The Legal Register is the central tool for this: per requirement it records the source, the scope of application, the affected security controls and the current implementation status, and supports filtering by jurisdiction based on recorded office locations and scope countries. The organisation’s approach to meeting these requirements and the individual responsibilities are set out in the respective topic-specific policies. Requirements identified as security-relevant are mandatorily considered when planning and designing business processes, applications and IT systems and when procuring new components; the legally responsible managers ensure compliance. When violations are detected, appropriate corrective actions are initiated and tracked via the CAPA register.

### 9.1 Where External Requirements Apply

External requirements are taken into consideration in the following activities:

- **Policies & Procedures:** When developing and updating information security policies and procedures, all applicable external requirements are incorporated and referenced.
- **Control Design:** When designing, implementing or changing information security controls, applicable legal and contractual obligations are taken as an input into the control decision.
- **Information Classification:** When classifying information and associated assets, external requirements (e.g. special categories of personal data, export control, secrecy obligations) are taken into account for both internal needs and supplier agreements.
- **Risk Assessment & Treatment:** Risk assessments and the selection of treatment measures take legal, regulatory and contractual obligations into account both as a risk source in their own right and as a boundary condition for treatment selection.
- **Processes & Responsibilities:** For each material external requirement, responsible processes and roles are defined and documented, in particular for notification duties (authority reporting, incident notification), data subject rights and retention periods.
- **Supplier Requirements:** Contractual requirements for suppliers are set as part of the supplier security assessment, depending on the type and scope of the products and services supplied (see Supplier Security Policy).

### 9.2 Handling of Legislation & Regulations

- **Identification of Relevant Legislation:** All laws and regulations relevant to the information security of the organisation are identified and recorded in the Legal Register. The identification takes into account the business model, office locations, the data processed and the customer segments served.
- **Multiple Jurisdictions:** If the organisation does business in several countries, uses products and services from other countries or transfers information across jurisdictional borders, the regulations of all relevant countries are taken into account. The Legal Register allows filtering by jurisdiction.
- **Regular Review:** The identified legislation and regulations are reviewed regularly to keep track of changes and to pick up new regulations. The review is performed at least annually as part of the management review and on an ad-hoc basis whenever relevant legal changes become known. Ongoing maintenance is the responsibility of the ISO in coordination with the relevant subject matter experts; in larger organisations the task may be delegated to a Compliance Officer who maintains regular exchange with the ISO.
- **Documented Processes & Responsibilities:** For each relevant requirement, the specific processes and individual responsibilities needed to meet it are defined and documented.

### 9.3 Cryptography & Legal Requirements

Cryptographic methods are subject to specific legal requirements. The following aspects are taken into account:

- **Import/Export of Cryptographic Hardware and Software:** Restrictions on the import or export of hardware and software providing cryptographic functions are observed (export control, dual-use regulation).
- **Retrofittable Cryptography:** Hardware and software designed so that cryptographic functions can be added to it is also subject to export control provisions and treated accordingly.
- **Usage Restrictions:** Usage restrictions on cryptographic methods in particular jurisdictions are taken into account when designing cryptographic controls (see Cryptography Policy).
- **Mandatory or Discretionary Authority Access:** Mandatory or discretionary methods of access by authorities to encrypted information are determined with legal counsel for every country in which encrypted information is stored or transferred and considered for data storage and transfer; the check before cryptographic techniques are used is governed by the Cryptography Policy.
- **Validity of Digital Signatures and Certificates:** The validity of digital signatures, seals and certificates in the relevant jurisdictions (e.g. eIDAS in the EU) is decisive for the selection and use of such services.

When moving encrypted information or cryptographic tools across jurisdictional borders, legal advice is obtained prior to transfer if legal admissibility is unclear.

### 9.4 Contractual Requirements

Information security requirements stem from:

- **Customer Contracts:** Contractual information security obligations towards customers (Data Processing Agreements, SLAs, confidentiality undertakings) are identified and factored into control design.
- **Supplier Contracts:** Contractual obligations with suppliers are referenced in the Legal Register and feed into supplier assessment in accordance with the Supplier Security Policy.
- **Insurance Contracts:** Information security requirements arising from insurance contracts (in particular cyber insurance, liability) are captured and considered in control design.
- **Legal advice where the legal position is unclear:** Where the legal position is unclear, legal advice is obtained before acting. This applies in particular when encrypted information or cryptographic methods cross a national border, and the advice is recorded in the legal register.

Where exceptions to the rules derived from these requirements are necessary in individual cases, the exception is recorded via the Exemption Request workflow, accompanied by a risk assessment, and authorised by the ISO as the sole formal approver. All exemptions are time-limited and monitored until expiry. The compliance management system is reviewed for efficiency and effectiveness as part of the annual independent review (see A 5.35).

## 10. Independent Review of Information Security (A 5.35)

The organisation’s approach to managing information security and its implementation (including the information security policy, topic-specific policies, roles, processes and controls) is reviewed independently at planned intervals and when significant changes occur. Completeness and update reviews of the security concept take place at least annually and on an event-driven basis. The internal audit programme is maintained as a dedicated document titled *Internal Audit Programme*, which sets the scope, planning mode, audit cycle, number of audits per year and audit ordering.

### 10.1 Conducting the Reviews

- **Management Planning & Initiation:** Top management appoints a person responsible for planning audits and revisions and ensures that no conflicts of interest arise. Top management plans the independent reviews in a multi-year internal audit programme that derives audit objectives from the organisation’s objectives and information security objectives, and formally initiates them. Each review assesses opportunities for improvement and the need for changes to the information security approach, including the information security policy, topic-specific policies and other controls. Before each audit, the audit object and audit objectives are defined and the affected personnel informed.
- **Independence of Reviewers:** Independent reviews are carried out by individuals independent of the area under review (internal audit function, an independent manager or an external audit organisation). The person conducting the review is not in the line of authority of the area under review, in order to ensure the independence of the assessment. Where external service providers are commissioned for an audit or revision, they are checked for independence and bound by confidentiality. The audit team never actively intervenes in systems during on-site reviews and does not issue instructions to make changes to the audit object.
- **Competence of Reviewers:** Reviewers have the appropriate technical competence for the subject under review. Competence is assessed based on education, certifications and professional experience; the audit team size matches the audit scope.
- **Reporting to Management:** The results of independent reviews are summarised in a written audit report and reported to the management that initiated them and, where appropriate, to top management. The ISO includes the audits and revisions performed and their results in the regular report to top management. Audit reports are retained as records.
- **Corrective Action on Deficiencies:** Where an independent review identifies that the organisation’s approach or implementation of information security is inadequate (e.g. documented objectives and requirements are not met or are not compliant with the direction stated in the information security policy and topic-specific policies), management initiates corrective action. Deviations or deficiencies identified in the audit report are remediated within an appropriate timeframe; corrective actions, including their timeline and ownership, are tracked in the CAPA register. For severe deviations, the audit team verifies the implementation of the corrective actions.
- **Review process:** Independent reviews follow a process described in the audit programme: trigger, cadence, scope, reviewers, form of the findings and recipients of the results. The process is approved and reviewed annually.
- **Scope of the review:** Reviews cover both the approach to managing information security (policy, objectives, roles, risk process) and its implementation across people, processes and technologies. For each review cycle it is recorded which review covered which of these levels.

### 10.2 Event-Triggered Reviews

In addition to scheduled reviews, an independent review is conducted on an ad-hoc basis when:

- **Changes in Legislation:** Laws and regulations affecting the organisation change materially.
- **Significant Incidents:** A significant information security incident occurs that points to systematic weaknesses.
- **New or Changed Business Lines:** The organisation starts a new business line or materially changes an existing one.
- **New or Changed Products and Services:** The organisation starts to use a new product or service, or materially changes the use of an existing one.
- **Material Changes to the Security Approach:** The organisation changes its information security controls and procedures materially.

Each audit follows a structured sequence: opening meeting, document review, risk-based sampling, on-site review with structured interviews, review of the risk treatment plan and closing meeting. External audit reports (from certification, third-party and customer audits) are recorded as a dedicated record and capture auditor, framework, audit period, findings classified according to the scheme described below, certificate details and summary.

### 10.3 Classification of Audit Findings

Findings from internal and external audits are classified according to the severity levels of ISO 19011. The classification determines the resulting actions:

- **Major Nonconformity:** A systemic failure to meet a requirement from ISO/IEC 27001 Annex A, a binding policy or a legal obligation. Major nonconformities are mandatorily tracked as corrective actions and verified before the next audit.
- **Minor Nonconformity:** An isolated failure to meet a requirement without direct systemic impact. Minor nonconformities are recorded as corrective actions with a due date.
- **Improvement Potential:** A functioning implementation with scope for optimisation. Improvement potentials are referred to the responsible person for decision and, when accepted, tracked as improvement actions.
- **Observation:** A factual statement without a conformity verdict. Observations feed as context into future audits, management reviews and risk analyses.
- **Positive Aspect:** A particularly effective control or established practice. Positive aspects are highlighted in the audit report and carried forward as good practice into the management review.
- **Remark:** Supplementary comment from the audit team below the threshold of a nonconformity.

### 10.4 Tracking of Corrective and Preventive Actions

Every deviation is tracked as a corrective or preventive action in the Corrective and Preventive Action register. Each action carries a binding due date, a responsible person and a reference to the originating audit and the affected security controls.

- **Due-Date Monitoring:** Overdue actions are picked up at the following audit and reviewed before the current review begins.
- **Effectiveness Verification:** After implementation, the effectiveness of the action is verified against measurable criteria and evidence; the result is documented and reflected in the next audit report.
- **Management Reporting:** The status of open and completed actions arising from audits is part of the ISO’s regular reporting to top management and feeds into the management review.
- **Escalation for Major Nonconformities:** For major nonconformities, the audit team actively verifies the implementation, either in a dedicated follow-up meeting or as a standalone checkpoint in the subsequent audit.

## 11. Compliance with Policies, Rules & Standards (A 5.36)

Compliance with the information security policy, topic-specific policies, rules and standards is verified primarily through internal audits and management reviews. Policy completeness, approval status and review timeliness are tracked via a documentation register that flags missing approvals, outdated versions and language gaps. Whether the rules are actually lived in day-to-day operations is assessed through manual review during internal audits and management reviews, supported by metrics from operational tickets, incident records and vulnerability management. For every policy, rule and standard it is defined how compliance is checked: by sampling, by reviewing records or by automated checks. Where a check can be automated, for instance through configuration comparison or log evaluation, it is automated.

### 11.1 Non-Compliance Response

When non-compliance is found as a result of a compliance review, the following steps are taken:

- **Root Cause Analysis:** When non-compliance is identified, the causes are investigated to determine whether the issue stems from a policy gap, a process failure, a training deficiency, a resource constraint or wilful disregard.
- **Corrective Action Planning:** The need for corrective action is evaluated based on the severity, scope and risk impact of the non-compliance. Corrective actions are documented with responsible owners, timelines and expected outcomes.
- **Corrective Action Implementation:** Appropriate corrective actions are implemented to address the root cause and prevent recurrence. Actions range from process adjustments and additional training to technical remediation and policy clarification.
- **Effectiveness Verification:** Corrective actions are reviewed to verify their effectiveness and to identify any remaining deficiencies or weaknesses. Verification is conducted after a defined period and documented with evidence.

Compliance review results and all corrective actions are recorded and retained as documented information at the time of the review. Managers report these results to the persons conducting independent reviews (internal audits) when such reviews take place in their area of responsibility. These records are handed to the independent review as input; they are not reconstructed for it afterwards. Every corrective action receives a deadline set by the risk of the non-compliance. If a corrective action is not completed by the next scheduled review, progress is documented and explicitly addressed at that review and in the management review.

## 12. Documented Operating Procedures (A 5.37)

Operating procedures for information processing facilities are documented in operational handbooks and made available to all personnel who need them. Procedures ensure the correct, consistent and secure operation of information processing systems. Operating procedures describe the actual operation and are adjusted when it changes. Changes to a procedure are approved through change management, and systems of the same kind are run according to the same procedure wherever possible.

### 12.1 When Procedures Are Required

Documented operating procedures are prepared for the following situations:

- **Standardised Activities:** Activities that are performed by multiple people and need to be executed consistently follow documented procedures to ensure uniform execution and prevent deviations.
- **Infrequent Activities:** Activities performed rarely are documented so that the correct procedure is available when the activity is next required, even if the original operator is no longer available.
- **Risk-Critical Activities:** New activities or changes to existing activities that present a risk if performed incorrectly are documented before first execution. The documentation includes preconditions, step-by-step instructions and verification checks.
- **Personnel Handover:** When activities are transferred to new personnel, documented procedures ensure continuity of knowledge and consistent execution during the transition period.

### 12.2 Procedure Content Requirements

Each operating procedure specifies the following elements as applicable:

- **Responsible Persons:** Each procedure identifies the responsible person or role, including required competencies and authorisation level.
- **Installation & Configuration:** Procedures for the secure installation and configuration of systems document baseline settings, hardening requirements and verification steps.
- **Information Processing:** Both automated and manual processing and handling of information follow documented procedures that specify input validation, processing steps and output verification.
- **Backup & Resilience:** Backup procedures define scope, schedule, method, storage locations and restoration testing requirements. Resilience procedures address failover and recovery steps.
- **Scheduling & Dependencies:** Procedures specify scheduling requirements and document interdependencies with other systems, including the sequence of operations and timing constraints.
- **Error Handling:** Instructions for handling errors, exceptions and unexpected conditions include diagnosis steps, escalation paths and recovery procedures.
- **Support & Escalation Contacts:** Each procedure lists internal support contacts and external support contacts (vendors, service providers) with escalation paths for unexpected operational issues.
- **Storage Media Handling:** Procedures for handling storage media cover classification-appropriate storage, transport, sanitisation and disposal requirements.
- **System Restart & Recovery:** Recovery procedures for system failures document the restart sequence, integrity checks, data verification steps and service restoration confirmation.
- **Audit Trail & Log Management:** Procedures for managing audit trails, system logs and monitoring records define retention periods, access controls, integrity protection and archival methods.
- **Monitoring Procedures:** Capacity, performance and security monitoring procedures specify what is monitored, the monitoring tools used, threshold definitions, alerting rules and response actions.
- **Maintenance Instructions:** Scheduled and ad-hoc maintenance procedures include pre-maintenance checks, maintenance windows, change approval requirements, rollback plans and post-maintenance verification.

Documented operating procedures are reviewed and updated when needed. Changes to procedures are authorised by the responsible person or role. Where technically feasible, information systems are managed consistently using the same procedures, tools and utilities to reduce configuration drift and operator error.

### 12.3 Records & Evidence

Records generated by ISMS processes are retained as documented information to provide evidence of conformity and effective operation. The following categories of records are managed:

- **Audit Records:** Internal audit reports are created as records linked to each audit event, based on the Internal Audit Programme. External audit reports (certification audits, third-party audits, customer audits) are documented with auditor, framework, audit period, findings by severity, certificate details and executive summary. Corrective actions resulting from audits are tracked in the Corrective Actions & Improvement Register.
- **Incident Records:** Security incident reports, investigation findings, evidence with chain of custody and post-mortem analyses are maintained by the incident management process.
- **Training Records:** Training completion is captured per user, including module, completion date, score and duration. These records serve as training evidence; competence is verified through assessments at the end of each training module.
- **Management Review Records:** Management review meetings capture minutes, decisions, action items, KPI snapshots and follow-up status.
- **Risk Records:** Risk assessments, treatment plans and residual risk acceptances are maintained in the risk register. Point-in-time snapshots of the risk register are produced at each management review and internal audit cycle.
- **Workflow Records:** Completed operational tickets serve as approval and change records. In particular, Change Management tickets capture the change request, impact assessment, approval, implementation evidence and post-implementation notes as structured records. Tickets are retained as documented information and made available for audits on request.
- **Assessment Records:** Completed checklists, self-assessments and responses (including remote workplace assessments, project security assessments and decommissioning checklists).
- **Policy Acknowledgement Records:** Signed policy acknowledgements produced via the acknowledgement mechanism (see Section 3.6).

### 12.4 Storage & Preservation

Policies and records are stored in the organisation's document management system. Each approval creates a new version; earlier versions are preserved and remain legible, including after being marked obsolete. Legibility outside that system is provided through a PDF output, which is generated on demand from the stored version; for audits, the required versions are exported as a bundle.

### 12.5 Retention & Obsolete Documents

Documents and records are retained for a minimum period consistent with applicable statutory, regulatory and contractual requirements. The retention defaults are reviewed against the Legal Register and the data retention plan; longer statutory periods take precedence where they apply. Retained documents and records remain queryable for audit and historical reference even after being marked obsolete.

Obsolete versions are also marked explicitly by document owners when a newer approved version supersedes the previous one. Newer approved versions take precedence in the documentation view. Obsolete versions remain visible in the version history so that the audit trail is preserved.

## 13. Privacy and Protection of PII (A 5.34)

The organisation identifies and meets the requirements for the protection of personally identifiable information that follow from the applicable laws, regulations and contracts. The rules are set out in the privacy policy and the procedures of the privacy information management system; this policy defines which documents carry them and refers to them.

### 13.1 Responsible documents of the privacy information management system

- **Privacy policy:** The topic-specific policy on the protection of personal data is the privacy policy of the privacy information management system. It is approved and communicated to all staff, processors and other interested parties; acknowledgement is recorded.
- **Procedures:** The procedures for protecting personal data are the standard operating procedures of the privacy information management system on data subject rights, consent, privacy impact assessment, transfers and processors. They are in operation, and everyone who processes personal data has been briefed on them.
- **Roles and responsibilities:** The privacy roles are assigned to named persons in the role matrix. Their fulfilment is assured through the reviews of the privacy information management system, the internal audits and the report to top management.
- **Responsible person:** The organisation has appointed a person responsible for the protection of personal data (data protection officer or an equivalent role). The appointment is recorded with its date and scope, and the contact is published internally and towards data subjects.
- **Applicable law:** The privacy laws that apply to the organisation are recorded in the legal register; the obligations that follow from them are assigned to the privacy roles and reviewed annually and whenever the legal position changes.
- **Technical and organisational measures:** The measures protecting personal data are recorded per processing activity in the privacy information management system and reviewed for appropriateness with every change and at least annually.
- **Privacy information management system:** The organisation operates a privacy information management system in line with ISO/IEC 27701 that brings policy, procedures, roles and measures together. It complements the ISMS; overlapping content is maintained in one place and used in both systems.

## 14. Roles & Responsibilities

- **Top Management:** Approves the Information Security Policy and ensures adequate resources are allocated for documentation activities. Bears overall accountability for the ISMS documentation framework.
- **Information Security Officer (ISO):** Maintains the documentation framework, coordinates policy reviews, monitors document completeness and reports documentation status to management. Acts as the sole formal approver for exemption requests.
- **Data Protection Officer (DPO):** Reviews documentation for data protection compliance and advises on retention requirements for records containing personal data.
- **Document Owners:** Each policy and procedure has a designated owner responsible for keeping the document current, initiating reviews and processing change requests. Owners ensure their documents reflect current practices and requirements.
- **Reviewers & Approvers:** Review documents for accuracy, completeness and compliance before approval. Approvers authorise publication of new or updated documents.
- **All Employees & Contractors:** Read, understand and acknowledge applicable policies and procedures. Report documentation gaps or inaccuracies to the document owner or the Information Security Officer.

## 15. Review & Maintenance

This policy is reviewed:

- At least annually, as part of the ISMS management review cycle.
- When the documentation framework or tooling changes significantly.
- When audit findings identify documentation control weaknesses.
- When new regulatory requirements affect document retention or control procedures.
