Skip to content

Latest commit

 

History

History

05-Project-05

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 

README.md

05 — Information Security Policy Pack

Six draft policies with 73 testable requirements, ownership distributed across the functions that must operate them, and nothing claimed to be in force.

Clause Stage Status Policies Approval

Folder 05-Project-05/
PDCA stage Do
ISO/IEC 27001:2022 Clause 5.2 — Policy; Clause 7.5 — Documented information
Status Delivered — pack submitted for approval 04-Sep-2026; approval pending
Consumes Project 01 scope · Project 02 issues · Project 03 risks · Project 04 controls
Feeds into Control implementation, awareness training, evidence generation, internal audit

Purpose

Clause 5.2 requires top management to establish an information security policy. Clause 7.5 requires documented information to be controlled — identified, versioned, owned, approved, and reviewed.

This project produces both: six policies that state what is expected of people, under document control that makes it possible to say which rules were in force and when. It exists because of internal issue INT-04 recorded in the context determination: SecureBridge's security rules were held informally, across several locations, with no owner, version, or review date. Personnel could not reliably be told what was expected of them, and the organization could not demonstrate what applied.

The pack opens the Do stage. The first four projects decided what the organization would do; this is the first that tells anyone.


Deliverables

Deliverable File Format
Information Security Policy Pack — introduction, document control, six policies, ownership, relationships, records documents/information-security-policy-pack.docx · Markdown Word (16 pages) + Markdown
Policy Register — register, all 73 requirements, all 51 records, relationships, ownership, framework completeness spreadsheets/policy-register.xlsx Excel, 7 sheets
Policy Framework Map — the six policies with owners, risks, and controls diagrams/policy-framework-map.svg SVG
Policy Lifecycle — draft to review, with the six review triggers diagrams/policy-lifecycle.svg SVG
Policy Pack Approval Submission — drafting record, consistency checks, six points raised evidence/policy-approval-submission.md Markdown
Evidence Index — pack evidence plus the position on all 51 identified records evidence/evidence-index.md Markdown

The Six Policies

Policy framework map

Policy ID Owner Approved by Requirements
Information Security Policy SBT-POL-01 ISMS Manager Managing Director 10
Access Control Policy SBT-POL-02 IT & Infrastructure Manager ISMS Manager 12
Information Security Incident Reporting Policy SBT-POL-03 ISMS Manager Managing Director 12
Acceptable Use Policy SBT-POL-04 Human Resources Manager ISMS Manager 13
Backup and Recovery Policy SBT-POL-05 IT & Infrastructure Manager Chief Technology Officer 13
Remote Working Policy SBT-POL-06 Human Resources Manager ISMS Manager 13

Each policy carries the full metadata block and the nine required sections: purpose, scope, policy statement, roles and responsibilities, mandatory requirements, exceptions, non-compliance, monitoring and review, and related documents and records.

Ownership is distributed across three roles and approval across three roles — a policy is owned by the function that must operate it. Concentrating everything in the ISMS Manager would have produced policies written by someone who does not do the work.


Requirements That Can Actually Be Tested

Access Control Policy

Policy B, rendered from the actual Word deliverable.

The 73 requirements are written so that an auditor could check them. Compare:

❌ "Employees must keep information secure."

✅ "Personnel shall not share their account credentials with any other person, including colleagues, managers, and IT staff. No member of the organization has a legitimate reason to ask for another person's password."

Several requirements exist specifically because this is a cybersecurity services provider:

  • SBT-POL-04.5 — security testing and exploitation tooling may be used only on designated devices, only for engagements with written customer authorization, and only within the agreed scope
  • SBT-POL-02.9 — customer-supplied credentials are held only in the approved credential store, issued for the shortest period necessary, and the customer asked to rotate them at engagement close
  • SBT-POL-06.13 — working from a location outside India requires prior approval, since it may create obligations the organization has not assessed
  • SBT-POL-05.5 — backup credentials are held separately from production administrative accounts, so compromise of production cannot delete or encrypt backups

One Deliberate Position

SBT-POL-03 states that reporting an incident in good faith will not result in disciplinary action, including where the person reporting contributed to the incident. Failing to report, or concealing an incident, is treated differently.

This was debated during drafting and is recorded in the approval submission. A policy that punishes reporting produces silence, and silence is worse than the mistake it hides — particularly for an organization whose detection capability is aimed at its customers rather than at itself.


Ownership and Accountability

Ownership matrix

Sheet 5 of the register — owner, approval authority, implementation, and compliance monitoring for each policy.

Four distinct accountabilities are recorded separately for every policy, because they are genuinely different jobs: who owns the content, who approves it, who implements it, and who monitors compliance. For SBT-POL-06 these fall to four different roles.


Document Control and Review

Policy lifecycle

All six policies sit at stage 2 — submitted, not approved. Every policy carries Version 1.0, Status Draft, proposed effective date 04-Sep-2026, next review 04-Sep-2027, and review at least annually.

The annual date is a floor, not a ceiling. Six triggers require review ahead of schedule: a significant security incident; a significant change to systems or services; a change in legal, regulatory, or contractual requirements; a major organizational change; a change to the risk assessment or Statement of Applicability; and an internal audit or management review finding that a policy is not being applied.


Policy Relationships

Every policy traces to at least one assessed risk and at least one Annex A control.

Policy Main risks addressed Annex A controls
SBT-POL-01 All ten — establishes the framework rather than treating one risk A.5.1
SBT-POL-02 RSK-001, RSK-004, RSK-008 A.5.15, A.5.17, A.5.18
SBT-POL-03 RSK-002, RSK-003, RSK-005, RSK-006 A.8.16, A.5.24*
SBT-POL-04 RSK-002, RSK-004, RSK-006 A.5.17, A.6.3
SBT-POL-05 RSK-002, RSK-005, RSK-010 A.8.13, A.5.30*
SBT-POL-06 RSK-001, RSK-002, RSK-004 A.5.15, A.5.17, A.6.7*

* Identified in SBT-SOA-01 as expected applicable but not yet assessed — a recorded gap, not an oversight.


What Is Not Claimed

This is the part that matters most for credibility:

  • No policy has been approved. All six are drafts. The effective date is the date proposed on approval.
  • No policy has been issued or acknowledged. Personnel have not been given these rules and cannot be held to them.
  • None of the 51 identified records is claimed to exist. The policies create the requirement for those records; the evidence index records that 4 record groups are partial and 4 require evidence entirely.
  • The framework is incomplete. Six of an intended fourteen policies are drafted. The remaining eight are named in the pack and in the register.
  • No certification. The organization is not certified to ISO/IEC 27001 and no external audit has been performed.

Role in the Portfolio

Context → Scope → Risk assessment → SoA → Policies
 INT-04     boundary    10 risks       12 controls   6 drafts, 73 requirements
Feeds into What it carries forward
Do stage — control implementation 73 requirements that name what must be established, with owners
Do stage — awareness and training Acknowledgement and training records the policies require
Do stage — evidence generation 51 identified records, almost none of which exists yet
Check stage — internal audit Testable requirements give the audit something objective to test against
Act stage — management review Approval status, acknowledgement coverage, and framework completeness
Project 11 — integrated view SBT-POL-NN identifiers feed the integrated ISMS manual

Skills Demonstrated

  • Writing enforceable requirements — 73 statements each testable by an auditor; vague obligations rewritten or removed
  • Distributed ownership — policies owned by the function that operates them, with owner, approver, implementer, and compliance monitor recorded separately
  • Document control — identifier, version, status, owner, approval authority, effective and review dates, review frequency, retention, applied uniformly
  • Sector-specific policy design — requirements covering testing tooling, customer credential handling, and cross-border working that would be disproportionate elsewhere
  • Cross-referencing without duplication — a requirement appears in one policy and is referenced from others, checked during consistency review
  • Culture-aware drafting — a no-blame reporting clause adopted deliberately, with the reasoning recorded
  • Honesty about status — nothing approved, nothing issued, no record claimed to exist, framework stated as incomplete

Assumptions and Illustrative Data

# Assumption Type
A-01 All six policies are drafts. None has been approved, issued, acknowledged, or implemented Planned
A-02 The effective date of 04-Sep-2026 is the date proposed on approval, not a date any policy took effect Planned
A-03 The 51 records identified are records that should be maintained; none is claimed to exist Illustrative
A-04 The drafting record, consistency checks, and points raised in the approval submission describe a fictional process Illustrative
A-05 Requirements depending on arrangements not yet in place — credential store, access review cycle, approved software catalogue, quarterly restoration testing — state what will apply once approved Not Yet Implemented
A-06 Eight further policies are needed; their identifiers are indicative and would be confirmed when drafted Planned
A-07 The organization is not certified to ISO/IEC 27001 and no external audit has been performed Not Yet Implemented

Known Gaps Carried Forward

Ref Gap Owner Target
EV-038 Pack submitted but not approved — no policy is in force and no requirement is binding ISMS Manager 30-Sep-2026
EV-039 No policy issued and no acknowledgement collected Human Resources Manager 31-Oct-2026
EV-040 No controlled document location exists, so version control cannot be demonstrated ISMS Manager 31-Oct-2026
EV-041 Eight of fourteen policies not drafted — a partial framework leaves recognized risks without a stated rule ISMS Manager 30-Nov-2026

Part of the SecureBridge ISO 27001 GRC Portfolio · SecureBridge Technologies Pvt. Ltd. is a fictional organization created for portfolio purposes. All policies are drafts prepared for management approval; none has been approved or implemented. No certification has been achieved and no external audit has been performed.