# Security Fundamentals

> **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]

> **Entry-level policy.** This document summarises the minimum information security requirements in compact form, with one section for each of the ten areas of measures under Art. 21(2) NIS2 (Section 30(2) BSIG). It suits small organisations and the start of an ISMS. The 21 topic-specific policies of the Starter Kit deepen each section; where a topic-specific policy is in force, its provisions apply.

## 1. Legal/Regulatory Basis

Directive (EU) 2022/2555 (NIS2), Art. 21(2), and Section 30(2) of the German BSIG: risk management measures in ten areas.

ISO/IEC 27001:2022, clause 5.2 and Annex A 5.1: information security policy and topic-specific policies.

Additional jurisdiction-specific laws and regulations applicable to [YOUR_ORGANISATION_NAME] are listed in the Legal Register and incorporated by reference.

## 2. Purpose and Scope

These Security Fundamentals describe the binding minimum requirements for information security at **[IHR_ORGANISATIONSNAME]**. They sit between the Information Security Policy (which states the security objectives and management commitment) and the thematic policies (which detail individual subject areas).

The scope of this document covers all information assets, processes, systems, and personnel within the defined ISMS scope as documented in the Scope Statement.

*Detailed provisions are set out in the thematic policies (Access Control, Cryptography, HR Security, Supplier Security, etc.), where these have been issued. In their absence, the requirements stated here apply directly.*

## 3. Risk Management

The organisation operates a systematic information security risk management process. Risks are identified, assessed, and treated on a defined cycle and whenever significant changes occur (new processes, new technologies, new suppliers, incidents, regulatory changes).

Risk assessment criteria are documented in the Risk Management Policy. Risk treatment decisions follow the established organisational risk appetite (currently set to **[RISK_APPETITE, e.g. balanced]**). The effectiveness of the implemented risk controls is evaluated periodically.

The Statement of Applicability identifies the applicable information security controls. Each applicable control has an assigned implementation status and an accountable role.

*Detailed provisions on the risk methodology are set out in the corresponding thematic policy, where one has been issued.*

## 4. Incident Management

Information security incidents are detected, reported, assessed, contained, eradicated, and reviewed in a defined process. Every employee and external party with access to organisational systems knows the reporting channel for suspected incidents.

### Roles

The Information Security Officer (ISO) coordinates incident response. The Incident Response Team (IRT) is convened on demand and includes IT operations, communications, legal/data protection, and, where the incident affects business processes, the relevant process owners. Top management is informed without delay for severe incidents.

### Escalation

Suspected incidents are reported to the ISO or the IT helpdesk. The ISO classifies the incident according to severity (low / medium / high / critical) and triggers the escalation defined for that severity level. High and critical incidents trigger immediate notification of top management and the Incident Response Team.

### NIS-2 Reporting Deadlines

For significant incidents within the meaning of NIS-2 §32 BSIG, the following statutory deadlines apply:

- **Early warning** within 24 hours of becoming aware of the incident
- **Initial notification** within 72 hours, including initial assessment and severity
- **Final report** within one month, including root-cause analysis, taken measures, and cross-border impact assessment

The competent NIS-2 reporting authority is recorded in the organisation's authority register: [REPORTING_AUTHORITY, e.g. BSI].

### Evidence Collection

For incidents that may require forensic analysis or legal action, evidence is collected and preserved according to a defined chain-of-custody procedure. Evidence is retained for at least the period defined in the data protection policy.

*Detailed provisions on incident response procedures, severity classification, and forensic handling are set out in the corresponding thematic policy, where one has been issued.*

## 5. Business Continuity and Crisis Management

The organisation plans and exercises the continuity of critical business processes and the recovery of supporting ICT systems for the event of disruption.

The organisation maintains a Business Impact Analysis (BIA) covering all business processes in scope. Each process has a defined Recovery Time Objective (RTO), Recovery Point Objective (RPO), and minimum operating mode.

### Continuity Roles

Top management is accountable for business continuity. The ISO coordinates the BCM programme. Process owners are responsible for the continuity of their respective business processes. The IT function is responsible for ICT recovery (disaster recovery plans, backups, restore tests).

### Minimum Continuity Requirements

- **Continuity plans:** Each critical process has a documented continuity plan covering manual workarounds, alternative locations, and minimum staffing
- **Disaster recovery plans:** Each critical ICT system has a documented recovery procedure including SLA-bound providers, backup locations, and tested restore steps
- **Backups:** Backups of essential data and configurations are taken on a defined schedule, stored separately from production systems, and restore-tested periodically
- **Exercises:** A tabletop or full-scale exercise is conducted at least annually; lessons learned feed back into the plans
- **Crisis communication:** Communication paths to employees, customers, suppliers, and authorities are predefined and reviewed at least annually

For organisations subject to NIS-2, business continuity measures are aligned with the requirements of §30 paragraph 2 BSIG, in particular continuity of operations during a security incident, restoration of normal operations, and the role of backup management.

*Detailed provisions on continuity plans, disaster recovery, and crisis communication are set out in the corresponding thematic policy, where one has been issued.*

## 6. Supply-Chain Security

The organisation manages information security risks arising from its relationships with suppliers, service providers, and ICT supply-chain participants.

All suppliers with access to organisational information, systems, or premises are listed in the Supplier Register. Each supplier is classified by criticality, type, and the kind of data or systems it accesses or processes.

### Supplier Roles

The Procurement / Contracting function owns the supplier-onboarding process. The ISO defines the security requirements that apply to suppliers based on criticality and data classification. Legal/Data Protection reviews the contractual basis (including DPA where applicable). The accountable business owner (process owner or asset owner) approves the engagement.

### Minimum Supplier Assessment Criteria

Before engaging a critical or high-risk supplier, the following aspects are evaluated:

- **Security posture:** evidence of an established information security management (certifications, audit reports, security questionnaires)
- **Compliance fit:** alignment with applicable regulatory frameworks (NIS-2, GDPR, sector-specific)
- **Contractual safeguards:** security and confidentiality clauses, incident-notification obligations, audit and termination rights
- **Data protection:** a Data Processing Agreement (DPA) is in place where personal data is processed
- **Continuity:** the supplier's own continuity capability is considered where the supplier supports a critical process

### Ongoing Monitoring

Critical and high-risk suppliers are reviewed at least annually. The review covers contract status, incidents involving the supplier, changes in service scope, and any cascading dependencies (sub-processors, fourth parties). Findings feed back into the supplier risk register.

*Detailed provisions on supplier evaluation procedures and contractual security clauses are set out in the corresponding thematic policy, where one has been issued.*

## 7. Acquisition, Development, and Vulnerability Management

Security requirements are considered when acquiring, developing, or operating information systems. Technical vulnerabilities of in-scope systems are tracked, prioritized, and remediated on a defined cycle.

System changes follow a documented change-management process. Updates and patches for operating systems and critical applications are installed in a controlled, timely manner. Where the organisation develops or commissions software, secure-development practices apply to those activities.

*Detailed provisions on IT operations, secure development, and vulnerability handling are set out in the corresponding thematic policy, where one has been issued.*

## 8. Effectiveness Evaluation and Continuous Improvement

The effectiveness of the ISMS is monitored continuously and reviewed at defined intervals. The risk assessment cycle is set to **[CYCLE, e.g. annually]**. Management Review is conducted **[FREQUENCY, e.g. quarterly]**.

Internal audits, security objective indicators, and incident metrics feed back into the continuous improvement process (CAPA, corrective and preventive actions).

*Detailed provisions on the audit programme and the management review procedure are set out in the corresponding thematic policy, where one has been issued.*

## 9. Training and Cyber Hygiene

All employees receive information-security awareness training appropriate to their role. Role-specific training is assigned to functions with elevated responsibilities (top management, ISO, IT administrators, HR, and process owners). Training participation is tracked, and refresh cycles are defined.

Cyber-hygiene fundamentals, strong authentication, locking of devices, safe handling of email and removable media, recognition of phishing, are part of mandatory baseline training and are reinforced by recurring awareness measures.

*Detailed provisions on the awareness programme and acceptable-use rules are set out in the corresponding thematic policy, where one has been issued.*

## 10. Cryptography

Cryptographic controls protect the confidentiality and integrity of information at rest and in transit. Approved algorithms and minimum key lengths follow current state-of-the-art recommendations. Cryptographic keys are managed throughout their lifecycle (generation, distribution, storage, rotation, destruction).

*Detailed provisions on cryptographic standards and key management are set out in the corresponding thematic policy, where one has been issued.*

## 11. HR Security, Access Control, and Asset Management

Personnel security applies across the employee lifecycle: pre-employment screening, signed confidentiality undertakings, onboarding and security training, role-based access provisioning, ongoing review of access rights, and a disciplined offboarding process including timely revocation of access and return of assets.

Access to information and information systems is granted on the principle of least privilege. Privileged accounts are separated from regular user accounts. Access rights are reviewed periodically by the accountable owner.

The organisation maintains an asset inventory for information assets, supporting assets (systems, suppliers, personnel), and physical assets. Each asset has an owner. Information is classified according to confidentiality, integrity, and availability requirements.

*Detailed provisions on HR security, access control, and asset management are set out in the corresponding thematic policy, where one has been issued.*

## 12. Multi-Factor Authentication and Secure Communications

Multi-factor authentication (MFA) is required for all privileged accounts and for remote access to organisational systems. MFA is also applied to user accounts whose access protects sensitive data, in line with the organisation's risk profile.

Communication channels for security-relevant exchanges (incident reporting, authority notifications, crisis communication) are predefined and protected appropriately, including the option to operate independently of compromised systems where required.

*Detailed provisions on endpoint security, network security, and crisis communication are set out in the corresponding thematic policy, where one has been issued.*

## 13. Entry into Force, Review, and Accountability

These Security Fundamentals are approved by top management and enter into force upon approval.

This document is reviewed at least annually and after any significant change to the organisation, the threat landscape, or applicable regulations.

Accountability for these Fundamentals rests with top management. The Information Security Officer maintains the document and coordinates updates.
