Asset Management & Information Classification Policy


Document Number: ISMS-POL-ASM-01

Classification: L1 — Policy (Domain)

Version: 0.1.2

Effective Date: February 20, 2026

Author: Lucas Shin — Security Director

Approved By: Richard — CISO

Next Review Date: February 2027

Parent Policy: Information Security Policy (ISMS-POL-ISP-01)


1. Purpose

This policy defines the requirements for identifying, classifying, managing, and protecting information and associated assets throughout their lifecycle within Cybercraft.

It ensures that all information assets are inventoried, assigned ownership, classified according to their sensitivity, and subject to appropriate controls proportionate to their value and risk.


2. Scope

2.1 Applicable Assets

2.2 Out of Scope


3. Information Asset Categories

Cybercraft operates a 100% cloud-based, Work from Anywhere (WFA) model with no physical offices, servers, or network infrastructure. Asset categories reflect this environment.

3.1 Cloud Platform Assets

CategoryExamplesPrimary Control
M365 TenantExchange, SharePoint, OneDrive, Teams, Entra IDM365 Workspace & Access Policy (M365 Workspace & Access Policy, ISMS-POL-M365-01)
Third-Party SaaSNotion, GitHub, Figma, AI toolsApplication & Data Governance Policy (Application & Data Governance Policy, ISMS-POL-ADG-01) + Supplier & Third-Party Security Policy (Supplier & Third-Party Security Policy, ISMS-POL-STP-01)
Cloud InfrastructureAWS (HVT), Cloudflare, VercelSupplier & Third-Party Security Policy (ISMS-POL-STP-01)

3.2 Data Assets

CategoryClassificationLocationGoverning Policy
Client engagement dataConfidentialM365 Private ChannelsISMS-POL-M365-01 §3
Internal strategy, contracts, financialsConfidentialM365 Private ChannelsISMS-POL-M365-01 §3
General business documentsGeneralM365 Standard ChannelsISMS-POL-M365-01 §3
Source codePer project classificationGitHubISMS-POL-ADG-01
Credentials & secretsConfidentialEntra ID, Key VaultsISMS-POL-M365-01 §7

3.3 Endpoint Assets (BYOD)

3.4 CA100 Appliance Assets

CA100 Appliance — ISMS Scope: To Be Determined (TBD)
AttributeDetail
OwnershipCybercraft-owned hardware, deployed at client sites
Data ownershipClient-owned data — Cybercraft acts as processor
Operation modelRemote management via Splashtop, data analysis and reporting
DecommissioningRedkey full disk wipe (NIS standard) — at initial deployment and service termination

If included in ISMS scope, additional controls required: Data Processing Agreement (DPA), remote access management procedure, and secure decommissioning procedure.

3.5 SaaS Category Classification

All SaaS platforms used for business purposes are classified into one of three categories based on the level of technical access control Cybercraft can enforce. This classification determines the applicable security controls and the types of data permitted on each platform.

CategoryNameClassification CriteriaTechnical Control Level
APlatformM365 native apps integrated directly with Entra ID✅ Full — MAM + CA + ADUE data isolation
BSAML-EnforcedSaaS with Enforced SAML on the current licence plan (self-login disabled; all authentication via Entra ID)⚠️ Auth boundary — Enforced SAML + Conditional Access; no in-app MAM
CUnmanagedSaaS where Enforced SAML is unavailable on the current licence plan (SMB/Free tier or SAML not offered)❌ Policy only — no technical enforcement possible
⚠️
Category is determined by the licence plan, not the product. The same SaaS may be Category B on an Enterprise plan and Category C on a Free/Team plan. Re-evaluate whenever a licence plan changes.

Information classification linkage:

SaaS Category assignment is recorded in the Information Asset Register (§4) under the SaaS Category property. Category-specific technical controls and account governance requirements are defined in Application & Data Governance Policy (Application & Data Governance Policy, ISMS-POL-ADG-01).


4. Information Asset Register

4.1 Register Requirements

Cybercraft shall maintain an Information Asset Register that records:

The register is maintained at: Information Asset Register (ISMS Documentation / 06-Asset Management)

4.2 Register Update Triggers

TriggerActionOwner
New SaaS tool adoptionAdd to register, classify, assign ownerSecurity Director
Personnel changeReview ownership assignmentsSecurity Director
Client engagement start/endReview client data assetsSecurity Director + CEO
Annual management reviewFull register reviewSecurity Director + CISO

4.3 Asset Discovery Methodology

Cybercraft's asset discovery operates on a contract-based acquisition model: all technology assets (SaaS, cloud services, infrastructure) enter the environment through deliberate procurement or administrative registration. This makes the primary discovery channel the onboarding process itself, not periodic scanning.

4.3.1 Technology Asset Discovery (SaaS / Cloud Services)

Primary discovery channel: Admin Consent Workflow in Entra ID.

📌
Separate periodic SaaS discovery procedure is unnecessary. With User Consent blocked and Admin Consent Workflow active, no SaaS application can enter the environment without administrator awareness. The Admin Consent Workflow serves as a continuous, real-time discovery channel. Legacy application cleanup is a one-time remediation activity — see Entra ID Enterprise Applications Governance (Entra ID Enterprise Applications Governance — SaaS Consent Controls and Inventory Cleanup) §7.

4.3.2 Endpoint Device Discovery

BYOD device discovery is handled through platform-specific management channels:

Periodic review of registered devices is performed as part of the Device Lifecycle Procedure (Device Lifecycle Procedure, ISMS-PROC-BYOD-01) §6 review cycle.

4.3.3 Reference

For detailed asset identification criteria, discovery entry points, and registration decision logic, see Information Asset Identification — Standard Definition (🔒 정보자산 식별 표준정의서 (Korean Source), ISMS-STD-ASM-01).


5. Asset Ownership

5.1 Ownership Principle

Every information asset must have a designated owner responsible for:

5.2 Default Ownership

Asset TypeDefault Owner
M365 tenant and Entra IDSecurity Director (Lucas Shin)
Client engagement dataCEO (Farah Herbert)
Third-party SaaS accountsSecurity Director
Source code repositoriesSecurity Director
Security policies and ISMS documentationSecurity Director
CA100 AppliancesSecurity Director

5.3 Ownership Review


6. Information Classification

6.1 Classification Scheme

Cybercraft uses a two-level classification scheme as defined in M365 Workspace & Access Policy (M365 Workspace & Access Policy, ISMS-POL-M365-01) §3:

ClassificationDefinitionM365 Minimum Requirement
ConfidentialData whose unauthorised disclosure would cause serious harm to Cybercraft, its clients, or partnersMust be stored in Private Channels
GeneralAll other business dataStandard or Private Channels
⚠️
Confidential data must reside in Private Channels, but not all data in Private Channels is Confidential. Private Channels may also contain General data where access restriction is desired for operational reasons. The classification of data within a channel is determined by its content, not by the channel type.

6.2 Classification Principles

  1. Platform-enforced access control: Data access is enforced by the M365 channel structure ("Platform = Policy" principle). Confidential data must be placed in Private Channels to ensure technical access restriction
  2. Channel Owner responsibility: Each Team/Channel Owner is responsible for classifying and managing the data within their channel(s). This includes determining what data is appropriate for the channel, managing membership, and ensuring Confidential data is not placed in Standard Channels or channels with Guest access
  3. No manual labelling: Microsoft Purview Sensitivity Labels are not deployed at current organisational scale (3–5 person SMB). This decision is documented and reviewed annually
  4. Default classification: All data is General unless the Channel Owner determines otherwise and places it in an appropriately access-controlled Private Channel
  5. Guest collaboration channels: Channels with external Guest participants are treated as General by design — the act of enabling Guest access implies the Channel Owner has determined the data is suitable for external collaboration. Users must not share data beyond the channel membership, enforced through user education and M365 sharing policies
  6. SaaS data classification: Data permitted on third-party SaaS tools is governed by the SaaS Category assigned to each platform (§3.5). Confidential data is restricted to Category A or B platforms; General data may reside on Category C platforms with compensating controls

6.3 Classification Review


7. Acceptable Use

Acceptable use requirements are distributed across domain-specific policies:

DomainGoverning PolicyKey Sections
BYOD devicesBYOD Security Policy (ISMS-POL-BYOD-01)§5 Acceptable Use
M365 platformM365 Workspace & Access Policy (ISMS-POL-M365-01)§3 Data Classification, §5 Teams Structure
Third-party applicationsApplication & Data Governance Policy (ISMS-POL-ADG-01)Account governance, AI data sovereignty
Communications and mediaCommunications & Media Security Policy (ISMS-POL-COM-01)Public disclosure, content security

All personnel must comply with the acceptable use terms defined in these policies.


8. Return of Assets

8.1 Upon Termination or Role Change

When an employee leaves Cybercraft or changes role:

  1. Selective Wipe of all Managed Volume / MAM-protected data — executed by Security Director via Intune
  2. Account disable in Entra ID within 24 hours of termination notification
  3. Licence reclamation — M365 licence reassigned or removed
  4. SaaS account review — third-party SaaS accounts associated with the individual are transferred, archived, or deactivated per Application & Data Governance Policy (ISMS-POL-ADG-01)
  5. CA100 access revocation — Splashtop access removed if applicable

8.2 Cross-reference


9. Media Handling

9.1 Digital Media

☁️
Cybercraft's 100% cloud model eliminates the need for routine use of removable storage media.

9.2 Disposal

Asset TypeDisposal Method
Cloud dataDeletion per M365 retention policies and SaaS provider data deletion procedures
CA100 ApplianceFull disk wipe using Redkey (NIS standard)
BYOD device (corporate data)Selective Wipe removes corporate data; personal device disposal is user responsibility

10. Compliance Mapping

ISO 27001 ControlRequirementCovered By
A.5.9Inventory of information and other associated assets§3 (Asset Categories) + §4 (Asset Register, incl. §4.3 Discovery Methodology)
A.5.10Acceptable use of information and other associated assets§7 (cross-ref ISMS-POL-BYOD-01 §5, ISMS-POL-M365-01 §3)
A.5.11Return of assets§8 (cross-ref ISMS-POL-HR-01, BYOD-PROC-01)
A.5.12Classification of information§6 (cross-ref ISMS-POL-M365-01 §3)
A.5.13Labelling of information§6.2 — Platform-enforced classification replaces labelling (documented rationale)
A.5.14Information transfer§7 (cross-ref ISMS-POL-COM-01, ISMS-POL-M365-01 §3.3)
A.8.26Application security requirements§3.5 (SaaS Category Classification — application security requirements driven by SaaS Category framework)

11. Document Control

VersionDateAuthorChanges
0.1.02026-02-20Lucas ShinInitial release — information asset categories (cloud/data/endpoint/CA100), register requirements, ownership model, two-level classification (cross-ref P1 M365), acceptable use (cross-ref delegation), return of assets, media handling
0.1.12026-02-23Lucas ShinAdded §3.5 SaaS Category Classification (A/B/C framework). Updated §6.2 SaaS data classification principle to reference §3.5. Added A.8.26 to compliance mapping
0.1.22026-02-25Lucas Shin§3.3 BYOD platform-specific visibility clarified (macOS ADUE → Intune Devices; Windows MAM-only → Entra ID + APP reports). §4.3 Asset Discovery Methodology added — contract-based acquisition model, Admin Consent Workflow as primary SaaS discovery channel, User Consent disabled rationale documented, endpoint discovery channels. A.5.9 compliance mapping updated. Cross-references to Standard Definition (ISMS-STD-ASM-01) §4.1/§6.5

Review Schedule


[End of Policy Document]