Turn the reviews your team repeats every week into automations. The agent runs them on schedule, reports what it found, and skips the run when nothing in the workspace changed.
The schedule, the evidence pull and the recurring task take care of themselves.
01
Write the check once, for example "list controls whose evidence changed this week", and run it hourly, daily, on weekdays or weekly.
Schedules use the owner's time zone and survive daylight saving changes; a dispatcher picks up due runs every minute.
02
Before a scheduled run starts, Secani checks the workspace's activity. No changes since the last run means no run, and no noise in your inbox.
If in doubt, the run starts anyway, and every automation runs at least once a week.
03
Connect an AWS account once. Secani checks root MFA, root access keys, AWS Config recording and Security Hub findings every day, without screenshots.
Secani assumes a cross-account role with an External ID and a session limited to four read actions.
The checks you would otherwise remember, start and screenshot yourself.
Running the same weekly review by hand
The agent runs it on schedule and reports what it found
Taking AWS console screenshots for evidence
Daily read-only collection from the AWS account
Reading quiet weeks for changes that never happened
Runs are skipped when nothing in the workspace changed
Creating the quarterly review task again
Recurring tasks created weekly, monthly, quarterly or yearly
How many recurring checks does your team run by hand?
Hours per year spent on recurring checks
75
Your numbers, multiplied: runs × minutes. Nothing of ours goes into the result.
A run can look and report. Changing things stays with people.
Automation runs use read-only tools. If the instructions would need a write or a decision, the run stops and asks for input instead.
Each run gets a 30-minute token issued for its owner, so it sees exactly what the owner may see and nothing more.
The run history shows status, instructions, result and why a run was skipped, for the last 30 days at a glance.
No. Runs use read-only tools. When the instructions need a write or an approval, the run ends asking for input, and a person takes it from there.
Hourly at a chosen minute, daily, on weekdays or weekly at a set time, or by hand with Run now. Each person can keep up to 200 automations per workspace.
Root account MFA, absence of root access keys, AWS Config recording status and Security Hub pass and fail counts per control, once a day. Free text and resource IDs from AWS are discarded.
Scheduled runs that only read workspace changes are skipped when nothing happened since the last successful run. Any doubt lets the run start, and each automation runs at least every 7 days.
Schedule it once and read the result.
