> For the complete documentation index, see [llms.txt](https://calvin-lai.gitbook.io/calvin-lai-security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://calvin-lai.gitbook.io/calvin-lai-security/iso-27001/documentation.md).

# Documentation

Meeting the ISO 27001 requirements involves a comprehensive set of documentation. Here’s a high-level overview of the key documents you’ll need to develop, maintain, and implement as part of your Information Security Management System (ISMS).

These documents collectively ensure that the organization’s ISMS is well-structured, systematically managed, and continually improved. They help demonstrate compliance with ISO 27001 and establish a solid foundation for managing information security risks effectively.

#### Mandatory Documents

1. **Scope of the ISMS (Clause 4.3)**
2. **Information Security Policy and Objectives (Clause 5.2, 6.2)**
3. **Risk Assessment and Risk Treatment Methodology (Clause 6.1.2)**
4. **Statement of Applicability (Clause 6.1.3 d)**
5. **Risk Treatment Plan (Clause 6.1.3 e)**
6. **Risk Assessment Report (Clause 8.2)**
7. **Definition of Security Roles and Responsibilities (Clause 5.3)**
8. **Inventory of Assets (A.8.1.1)**
9. **Acceptable Use Policy (A.8.1.3)**
10. **Access Control Policy (A.9.1.1)**
11. **Operating Procedures for IT Management (A.12.1.1)**
12. **Secure System Engineering Principles (A.14.2.5)**
13. **Supplier Security Policy (A.15.1.1)**
14. **Incident Management Procedures (A.16.1.5)**
15. **Business Continuity Procedures (A.17.1.1)**
16. **Legal, Regulatory, and Contractual Requirements (A.18.1.1)**
17. **Internal Audit Program (Clause 9.2)**
18. **Corrective Action Procedure (Clause 10.1)**

#### Mandatory Records

1. **Records of Training, Skills, Experience, and Qualifications (Clause 7.2)**
2. **Monitoring and Measurement Results (Clause 9.1)**
3. **Internal Audit Results (Clause 9.2)**
4. **Results of the Management Review (Clause 9.3)**
5. **Records of Nonconformities (Clause 10.1)**
6. **Records of Corrective Actions (Clause 10.1)**

#### Other Commonly Required Documents

1. **Risk Management Framework**
2. **Procedures for Document Control**
3. **Procedures for Control of Records**
4. **Procedure for Internal Audits**
5. **Procedure for Corrective Actions**
6. **Procedures for Incident Response and Management**
7. **Procedures for Business Continuity Management**
8. **Change Management Procedures**
9. **Backup and Recovery Procedures**
10. **Physical Security Procedures**
11. **Secure Development Procedures**

#### Guidelines and Best Practices (Optional)

1. **Guidelines for Risk Assessment and Treatment**
2. **Guidelines for Data Protection**
3. **Guidelines for Secure Communication**
4. **Guidelines for Remote Working Security**
5. **Guidelines for Managing Third-Party Suppliers**
6. **Guidelines for Secure Software Development**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://calvin-lai.gitbook.io/calvin-lai-security/iso-27001/documentation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.