SOC 2 · Slack
Approve sensitive SOC 2 changes in Slack
Deixic posts each sensitive change to the channel you choose, waits for a named approver to decide with a reason, and records the decision on the receipt.
Tests Deixic works on in Slack
Criteria touched: CC8.1 Change management, CC7.2 Monitoring and logging.
Failing testWhat Deixic doesCriterion
Changes are authorized before they are madePosts the change, the before state, and the policy section to Slack and holds it until a named approver answers.CC8.1
Failing controls are monitoredPosts when a control fails and when it passes again.CC7.2
Decisions are recordedWrites the approver, the reason, and the time onto the receipt.CC8.1
What runs, what waits, what is yours
Deixic classifies every Slack action before it runs.
Runs within policy
- Post a status message when a control fails or passes
Waits for a named approver
- Every sensitive change, until a named approver decides in the thread
Sent to you as a decision
- Decisions only your company can make are posted as a question with the options.
- Deixic does not fix anything in Slack. The fix lands in the system that owns the setting.
Read back and evidence
Each change is read back from Slack, attached to the test in your compliance platform (or kept in Deixic if you have none), and the test runs again.
Deixic reads back
- The approver's identity and answer from the thread
- The change as it reads in the target system after approval
Your auditor gets
- The approval thread with approver, reason, and time
- The receipt linked to the thread