Information Security Policy


Document Number: ISMS-POL-ISP-01

Classification: L1 — Policy (Master)

Version: 0.1.4

Effective Date: February 18, 2026

Author: Lucas Shin — Security Director

Approved By: Richard Williams — CISO

Next Review Date: February 2027


1. Purpose

This document is the top-level Information Security Policy for Cybercraft. It defines the overarching security principles, governance structure, and policy framework that guide all information security activities across the organisation.

All domain policies and L3 procedures derive their authority from this document.


2. Scope

2.1 Organisational Scope

This policy applies to:

2.2 Technical Scope

2.3 Regulatory & Standards Alignment

This ISMS is designed to align with:

2.4 Security Standards Framework — Base Reference

This ISMS is derived from Cybercraft's Security Standards Framework (Security Standards Framework), which defines two security profiles:

Cybercraft operates under the COM Profile. All Level 2 policies and Level 3 procedures in this ISMS implement COM Profile requirements, tailored to Cybercraft's specific organisational context and technical environment.


3. Information Security Principles

All security decisions across Cybercraft shall be guided by the following principles:

3.1 Zero Trust

Never trust, always verify. Access to corporate data is granted based on verified identity, device compliance, and contextual conditions — not network location or device ownership.

3.2 Platform = Policy

The Microsoft 365 platform structure itself serves as the primary mechanism for access control, data classification, and data segregation. Teams structure, licensing tiers, and Entra ID configuration are the implementation of security policy — not separate from it.

3.3 Least Privilege

Users are granted the minimum level of access required to perform their role. Access is controlled through a combination of:
- Licence tier assignment (determines available services)
- Teams membership and role (determines data access within services)
- Conditional Access policies (determines access conditions)

3.4 Proportionality

Security controls are proportionate to the size, nature, and risk profile of Cybercraft as a 3–5 person SMB. Policies are designed to be practical and operationally sustainable without dedicated security operations staff.

3.5 Defence in Depth

No single control is relied upon. Security is enforced through layered controls — identity verification, device compliance, application-level protection, and data-level restrictions.

4. Governance Structure

4.1 Roles and Responsibilities

RolePersonResponsibilities
Group ChairmanJeff HerbertGroup-level strategic oversight, cross-entity coordination between Cybercraft, Techtype, and HVT
CEOFarah HerbertExecutive sponsor of ISMS, final authority on business risk acceptance, resource allocation for security initiatives
CISORichard WilliamsPolicy approval, risk acceptance, annual management review, strategic security direction
Security DirectorLucas ShinPolicy development and maintenance, security architecture design, technical implementation, compliance monitoring, incident coordination
All PersonnelAll staffComply with all applicable policies and procedures, report security incidents, complete security awareness requirements

4.2 Management Review


5. Policy Framework — Document Hierarchy

The Cybercraft ISMS follows a four-level document hierarchy (L1 Policy → L2 Standard → L3 Procedure → L4 Guideline), derived from the Security Standards Framework (Security Standards Framework):

📐
Security Standards Framework — Base standard. Defines COM and DEF profiles, cross-profile guidelines (EXT-01, EXT-02, EXT-03), and consulting delivery models.

L1 Policy (Master) — This document. Applies the COM Profile to Cybercraft and defines principles, governance, and policy scope.

L1 Policy (Domain) — Domain-specific policies. Define requirements and controls for specific security domains.

L2 Standard — Measurable criteria and baseline definitions for specific domains.

L3 Procedure — Operational procedures. Define step-by-step implementation details under each domain policy.

L4 Guideline — User and administrator manuals and guidance documents.

5.1 Domain Policies

IDPolicyScopeStatus
P1M365 Workspace & Access PolicyLicence-tier-based access control, Teams structure design (L1/L2/L3), channel-based data segregation, CA/MAM per platform, admin rights📝 Draft — M365 Workspace & Access Policy (ISMS-POL-M365-01) Pending review
P2BYOD Security PolicyPersonal device enrolment, compliance, app protection, non-managed app controls, patching, monitoring, incident response✅ Complete — BYOD Security Policy (ISMS-POL-BYOD-01)
P3Application & Data Governance PolicyData context isolation, app account governance, ID governance (SSO/Federation/Sprawl), AI data sovereignty, technical roadmap✅ Complete — Application & Data Governance Policy (ISMS-POL-ADG-01)
P4Human Resource Security PolicyHiring verification, security awareness, NDA, termination/offboarding✅ Complete — Human Resource Security Policy (ISMS-POL-HR-01)
P5Supplier & Third-Party PolicySaaS tool security assessment, AI service evaluation, partner/subcontractor requirements, data sharing controls, cross-tenant security✅ Complete — Supplier & Third-Party Security Policy (ISMS-POL-STP-01)
P6Communications & Media PolicyYouTube/e-book content security review, public disclosure controls, brand protection✅ Complete — Communications & Media Security Policy (ISMS-POL-COM-01)
P7Business Continuity PolicyKey person risk, backup strategy, emergency contacts, disaster recovery✅ Complete — Business Continuity Policy (ISMS-POL-BCP-01)
P8Asset Management & Information Classification PolicyInformation asset inventory, ownership, classification scheme, acceptable use, return of assets, media handling✅ Complete — Asset Management & Information Classification Policy (ISMS-POL-ASM-01)
P9Incident Management PolicyIncident classification, detection, triage, containment, evidence collection, post-incident review (lessons learned), external notification✅ Complete — Incident Management Policy (ISMS-POL-INC-01)
P10Document Management PolicyDocument classification framework (4-purpose), Doc ID scheme, L-hierarchy definition, document governance (approval, review, retention)📝 Draft — Document Management Policy (ISMS-POL-DCM-01) Pending review

5.2 L3 Procedures (under P2)

IDProcedureParent Policy
BYOD-PROC-01Device Lifecycle ProcedureP2
BYOD-PROC-02Patch Management ProcedureP2
BYOD-PROC-03Access Control & Data Protection ProcedureP2
BYOD-PROC-04Monitoring & Incident Response ProcedureP2

6. Risk Management

6.1 Risk Assessment

Cybercraft shall conduct a formal risk assessment:

6.2 Risk Treatment

Identified risks shall be treated through one of:

All risk treatment decisions shall be documented and reviewed quarterly.


7. Security Incident Management

All personnel are required to:

  1. Report suspected security incidents to the Security Director within 24 hours
  2. Preserve evidence and avoid actions that may compromise investigation
  3. Cooperate with incident investigation and remediation activities

Detailed incident response procedures are defined in the relevant L3 procedures under each domain policy.


8. Compliance & Enforcement

8.1 Compliance Monitoring

8.2 Non-Compliance


9. Document Control

VersionDateAuthorChanges
0.1.02026-02-18Lucas ShinInitial release — established ISMS Level 1 policy and 6-policy Level 2 framework
0.1.12026-02-19Lucas ShinAdded §2.4 Security Standards Framework Base Reference with COM/DEF Profile definitions.
0.1.22026-02-20Lucas ShinL2 policy reordering: Infrastructure (P1) → Access (P2) → App/Data (P3) → People (P4) → External (P5) → Communications (P6) → Emergency (P7). Added P3 Application & Data Governance Policy. Updated all document numbers and cross-references.
0.1.32026-02-20Lucas ShinAdded P8 Asset Management & Information Classification Policy (ISMS-POL-ASM-01) and P9 Incident Management Policy (ISMS-POL-INC-01) to L2 policy framework. Total L2 policies: 9.
0.1.42026-03-03Lucas ShinAdded P10 Document Management Policy (ISMS-POL-DCM-01). Total domain policies: 10.

Review Schedule


[End of Policy Document]