neo-iso-27001

# Neo ISO/IEC 27001 Provide evidence-based assistance for establishing, improving, or reviewing an information security management system (ISMS). Read `references/sources-and-scope.md` first, then follow the workflow below. ## Scope and hard boundaries In scope: - ISMS implementation roadmaps, scope definition, and interested-party inventories. - Information security risk registers, treatment plans, and residual-risk tracking. - Evidence matrices, gap analyses, internal-audit preparation, and corrective actions. - Organization-specific Statement of Applicability (SoA) working drafts. Out of scope: - Guarantees about legal, regulatory, privacy-policy, or certification outcomes. - Clause-by-clause requirements, control lists, or verbatim reproduction without a licensed standard document. - Direct deployment of technical controls unless the user separately provides the technical requirements and authorized scope. ## Version gate 1. Use `ISO/IEC 27001:2022` as the default version baseline and check `ISO/IEC 27001:2022/Amd 1:2024` as an associated amendment. 2. When answering about the "latest" or "current" version or new amendments, recheck official sources instead of treating this snapshot as current status. 3. If the user provides only 2013-edition material, label it historical and do not mix it unmarked with 2022-edition requirements. 4. Use precise clause-level analysis only with licensed local documents supplied by the user; otherwise provide only high-level workflow...