Clerk.io

Asset & Configuration Management Policy

1. Purpose

Provide a framework for identifying, recording and maintaining Clerk.io assets and for ensuring that systems are configured according to approved security baselines.

2. Scope

3. Asset Inventory

  1. The authoritative inventory is managed in Linear CMDB and synchronised nightly by internal AI agents.
  2. Each asset record includes owner, classification, location and lifecycle status.
  3. New assets must be registered before being placed into service.
  4. For all production assets, the designated ultimate asset owner is the Head of Product, who is accountable for risk acceptance and prioritisation of remediation.
  5. Day-to-day operational management of production assets (including keeping inventory attributes current) is delegated to the SRE Lead.

4. Configuration Management

Phase Requirement
Baseline Definition SRE defines hardened images (CIS-benchmarked container base images).
Change Control Deviations require GitHub Pull Request, peer review and automated policy-as-code checks.
Versioning All IaC modules are semver-tagged; production environments pin to specific tags.
Drift Detection Daily configuration drift scans; Better Stack alert on unmanaged resources.

5. Hardening Standards

6. Monitoring & Review

7. Roles & Responsibilities

Role Responsibility
Head of Product Ultimate owner of all production assets and their associated risks
SRE Lead Day-to-day operational management of production assets; maintain IaC baselines and drift detection tooling
Information Security Manager Approve hardening standards & review exceptions
Asset Owners Keep asset metadata current; initiate decommissioning

8. Decommissioning

9. Exceptions

All exceptions documented in Linear SECURITY queue with compensating controls and expiry date.


Evidence IDs: INV-01, CFG-01, CFG-02 (see Controls Matrix).