Policies that match what you actually test.
Auditors compare your written policies against your controls and your evidence. Kmetog keeps all three connected, so a policy is never out of date with the checks that prove it is being followed.
Every policy statement points to the control that proves it.
When a policy says admin accounts require MFA, that sentence is linked to the MFA control and its latest result. Gaps between what you say and what you do surface on their own.
- Two-way links. Open a control to see its policy, or a policy to see its controls.
- Drift alerts. A control change that contradicts policy wording is flagged for review.
Changes reviewed, approved and kept on record.
Policies move through draft, review and approval with named approvers. Every published version is kept, so you can show which policy was in force on any date in the audit period.
- Approval workflow. Route drafts to the right approvers and capture sign-off.
- Review cycles. Annual or custom review dates with reminders to policy owners.
- Acknowledgements. Collect staff acknowledgement of key policies as evidence.
What teams usually ask
Do you provide policy templates?
Kmetog includes starting templates aligned to supported frameworks. They are a draft, not a finished policy, and should be adapted to how your business actually operates.
Can we import our existing policies?
Yes. Existing documents can be uploaded, versioned from that point and linked to controls.
Keep what you write and what you do in step.
Bring your current policy set to a demo and see how it links to the controls Kmetog tests.