Patched is a claim. Hardened is a scan.

What this replaces

• The inventory was accurate the day somebody exported it.
• Patched means it was said out loud in a status meeting.
• A setting drifts back to default and the audit finds it first.

What you do here

• 1Own the asset and process register.Create, edit and retire hardware, software and service entities, each one showing the source it was discovered from.Asset register
• 2Scan a system against its baseline.The hardening add-on runs the checks and lists every failure with its detail, per system, on a licensed tenant.Hardening scans
• 3Adjudicate an exception with a written rationale.A check that will never pass gets a decision and an owner instead of staying permanently red.Hardening exceptions
• 4Repeat the scan, then read the drift.Recurring scans, identity alerts and AI insights on a managed system show what moved since the last pass.Managed systems
• 5Turn a vulnerability into a patch task.Read the queue, raise the work item, own it to done: the queue is read-only, the task is not.Tasks
• 6Certify the access you were asked to review.You sit on the reviewer side of a certification campaign, approving or revoking the entitlements put in front of you.My reviews

What changes

• Seven tabs per managed system: setup, configuration, scans, findings, exceptions, identity alerts, AI insights.
• A baseline check is a pass or a fail, dated by the scan that produced it.
• Each asset shows the source it was discovered from, dated.

Where the role stops

You review access; you do not run the campaign. The systems are yours, the programme is not: no risk register, no compliance module, no control library.