Before
Compliance staff likely had to retrieve the employee list, review personnel records one by one, and inspect individual compliance checks manually. They then had to identify the failed requirements, translate them into understandable explanations, and copy the findings into a Slack notification.
How it works
- Retrieve the full employee list and iterate through each person’s compliance data.
- Evaluate each compliance check, distinguish failures from passing results, and map supported failure types to readable explanations.
- Send a Slack alert only when non-compliant findings exist; otherwise, complete the review without a notification.
Workflow details
- Daily intake: A daily trigger starts the workflow, which retrieves the full personnel list and prepares the employee records for individual review.
- Employee compliance review: Each employee is evaluated against their available compliance checks, including lock-screen settings, antivirus, hard-drive encryption, password manager status, auto-updates, accepted policies, identity MFA, background checks, agent installation, and security awareness training. Hardware is explicitly treated as not monitored in the decision path.
- Failure classification: The workflow distinguishes passing and failing checks, identifies the type of each failure, and converts supported failure codes into readable explanations for the affected employee.
- Alert filtering: Compliance findings are accumulated into a formatted output for each employee. If the combined output is empty, the workflow follows a success path; if findings exist, it proceeds to notification.
- Operational result: Non-compliance alerts are posted automatically to a Slack channel with the affected users and their specific compliance gaps, while successful runs return a completion result without creating an unnecessary notification.
What changed
The daily review now evaluates employee compliance and prepares failure-specific explanations automatically. Slack receives an alert only when the generated output contains findings, while compliant runs finish without requiring a human to assemble or send a message.
Work removed
Pulling the employee list, reviewing employees individually, checking each compliance status, identifying failed requirements, translating failure codes into explanations, compiling findings, deciding whether an alert is needed, and manually posting the results to Slack.
Expected outcome
One automated daily review can cover up to 10 defined compliance checks per employee and deliver failure-specific Slack alerts without manual compilation.
