Turtini

cATO: evidence, freshness and automated checks

Each control shows whether its evidence is current, expiring, expired, or missing.

How freshness works:
An evidence item is dated by when what it shows was true, not when it was uploaded, and is valid for a number of days. The default comes from the first control it supports: FedRAMP's continuous-monitoring periodicity for that control when you use a FedRAMP baseline, otherwise annually. You can set your own period per control or per item. Freshness is recomputed every time the page loads, so evidence goes stale on its own. Withdrawn items, unfinished uploads, and images held by moderation count for nothing.

Add evidence (Evidence tab):
1. Choose the kind: a link (https only), a file, or an attestation.
2. Name the controls it supports, such as AC-2 or AC-2(3).
3. Set the date it was true and, if you want, how long it stays valid.
4. For a file, choose it with Choose file. PDF, text, CSV, JSON, images and Office documents up to 25 MB. The server checks that the file matches what was declared and records its SHA-256. Images go through the platform's image moderation and cannot be opened until approved.
To retire an item, Withdraw it with a reason. The record stays, marked withdrawn.

Automated checks:
These read data Turtini actually holds and record the result as evidence:
- MFA enrollment (IA-2(1), IA-2(2)): passes when every member at editor or above has a second factor.
- Access roster (AC-2, AC-2(3), AC-6(7)): fails when a member has not signed in for more than 90 days and still holds access.
- Audit log integrity (AU-9, AU-9(3)): recomputes the Wally and API action ledger, this workspace's own activity log, and the Federation audit log if you use Federation.
- Turtini backups (CP-9) and Turtini container scan (RA-5, SI-2): what Turtini reports about its own operations as a provider your system uses. Counts and dates only. Provider-reported and not independently assessed; Turtini holds no ATO.
A check that cannot read its data says Not verified. It never reports a pass it could not confirm.

Planned, not built: Turtini regression-guard status and IAM drift (their results are not stored anywhere a running service can read), and Tenable, Splunk and AWS Config connectors.

Running checks:
Run runs one check now. Run checks runs every check whose evidence is missing, expired or about to expire. Nothing runs on a schedule in this release: the checks run as the person who presses the button, and there is no unattended re-check. Put a recurring reminder on the ISSO's calendar to press Run checks at least monthly.