A.5 Organizational controls

A.5.9 Inventory of information and other associated assets

Not mandatory by default – decided in your SoA

What it means in plain language

Know what information and assets you have (data, systems, devices, cloud services), who owns them, and keep the inventory current.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

An inventory fails when teams treat it as a one-time spreadsheet instead of a living control record. Gaps usually appear where cloud subscriptions, mobile devices, data repositories, and shadow services are owned informally or move between teams without update discipline. The operational connection between the Asset Register and Asset Management Procedure work together to expose ownership gaps, stale entries, and untracked assets before they become operational blind spots.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Asset register entries omit owners, so accountability for classification, review, and secure disposal cannot be traced when auditors sample a device or SaaS account.
  • Reconciliations are performed sporadically or only after incidents, leaving cloud consoles, MDM exports, and procurement records inconsistent with the stated inventory.
  • Data sets, removable media, and virtual assets are listed without location, business purpose, or lifecycle status, making it unclear which items remain in scope.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Describe an owner-first intake workflow: procurement, IT, and system administrators each submit new assets within a defined period, and the asset owner confirms purpose, classification, location, and retention context before activation. Include practical fields such as asset ID, service name, serial number, tenant, business process, and disposal trigger.
  • Use illustrative reconciliation checkpoints against MDM, cloud billing, endpoint management, and procurement logs. The Asset Management Procedure should explain who compares sources, how mismatches are triaged, and what corrective tasks are raised when an asset is missing, duplicated, or reassigned without an update.
  • State how classification and ownership changes are recorded when assets are transferred, retired, or repurposed. Show the evidence trail: change request, updated register row, approval from the named owner, and a record of any follow-up actions such as access review or data deletion.
  • Assign clear accountability to asset owners, IT operations, and information security for periodic review. Keep practical records such as quarterly sign-off lists, exception logs for unknown devices, and meeting notes where unresolved inventory discrepancies are escalated and tracked to closure.

What an auditor will ask to see

  • Asset Register export showing owner, classification, status, location, and last review date for servers, laptops, SaaS tenants, and shared repositories.
  • Quarterly reconciliation record comparing MDM, cloud console, procurement, and register entries, with resolved variance notes and assigned actions.
  • Approved Asset Management Procedure sections covering intake, ownership changes, reconciliation steps, and retirement updates with named responsibilities.

Baseline documents in the kit

These free kit documents help you document or evidence A.5.9. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.1 — User endpoint devices and A.5.33 — Protection of records. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.