Settings and policies

What it covers

• Settings are organised by domains: access/capabilities, maintenance windows, module lifecycle/visibility, worker thresholds, source/signature, firewall/network, remote allow-list/enrolment, hardware schedule/evidence retention, diagnostics/validation and audit retention.
• Runtime-changing settings follow Read → Plan → Apply and record actor, reason, old/new value and audit.
• Maintenance policy can warn/block restart/update/repair outside the window.
• Hardware-worker settings define frequency, evidence channels, timeout, load restrictions and vendor lookup.

How to use it

1. Read the current value.
2. Create a plan.
3. Check scope/impact.
4. Apply.
5. Verify runtime/audit.

Important rules

• Do not increase timeouts/allow-lists merely for a warning.
• Safe defaults change for a reason.
• Heavy evidence checks are scheduled according to host load.