4.0 Policies

The policy is the evidence

Authored, owned, approved and versioned in one place — and mapped to the controls it answers for, so publishing moves the numbers instead of filling a folder.

Asset Management PolicyDraftOrganization-wideAnnualNo review dateEveryoneSubmit for approval
FileView
Savedv1

Purpose

You cannot protect what you cannot see. Access reviews, vulnerability management, change control and incident response all begin by asking which systems exist and who is responsible for them, and every one of them is only as complete as the answer.

This policy sets out how the organization identifies its information assets, records them, assigns ownership of them, and manages them from acquisition through to disposal.

Scope

Applies to all employees, contractors and third parties who acquire, operate, hold or dispose of an asset on behalf of the organization. It covers end-user devices, servers, containers, databases, and the accounts, domains and cryptographic keys that make them reachable.

Roles and responsibilities

The policy owner owns the asset register as a whole and is accountable for its completeness. Asset owners are accountable for the individual assets recorded against their name.

The asset register

Every asset is recorded in a single register, whether a connector discovered it or a person entered it by hand. A record carries the asset’s name, its kind, its owner, its classification and its lifecycle state, and no record is complete without all five.

Classification

Every asset is classified when it is recorded and reclassified when what it holds changes. The classification decides what protection it gets, so an unclassified asset is treated as the most sensitive one it could be until somebody says otherwise.

Disposal

An asset leaves the register only once whatever it held has been destroyed or returned, and the record of its disposal outlives the asset itself.

  • 4.1

    Written where it is used

    Start from a template or from nothing. The document sits beside its owner, its approver and its review cycle rather than in a drive nobody opens.

  • 4.2

    Approved, not just saved

    Draft, submit, approve, publish, archive — every move stamped with who made it, and every version kept.

  • 4.3

    Mapped to controls

    A policy answers for Common Controls in both directions. Publishing it emits evidence against each one, so the score moves with no file to upload.

Provable today, not at audit time.

Run it yourself or have Bindsec run it for you. Either way, the evidence is current and the posture is one place.