Overview
Cremit's Slack integration enables real-time security alerts directly in your Slack workspace. Receive instant notifications when active secrets are detected, scan sources fail verification, or security incidents are created.
Step-by-Step Setup
Step 1: Add Slack Channel
- Navigate to Configuration > Alarms in your Cremit dashboard
- Click on the Channel tab
- Click Add Channel button
- Select Slack from available options (Slack, Webhook, Telegram)
1. Name: Enter a channel identifier (e.g., #security-alerts)
- This is for your reference in Cremit
2. Description: (Optional) Add a description (e.g., "Security team alerts channel")
3. Click Create Channel
Step 3: Authorize Slack Integration
After clicking "Create Channel", you will be automatically redirected to Slack to complete the OAuth authorization:
- Authorize Argus (Cremit) to access your Slack workspace
- Select the Slack channel where you want to receive notifications
- Confirm authorization
Once authorized, you'll be redirected back to Cremit and the channel will be ready to use.
Note: If you prefer using Slack Incoming Webhook instead of the OAuth app, select the Webhook tab in the Channel setup.
Step 4: Create Alarm Rules
Now that your Slack channel is connected, configure when you want to receive notifications:
- Navigate to Configuration > Alarms > Alarms tab
- Click Create Alarm or New button
- Configure the alarm settings:
Alarm Channels:
- Select the Slack channel you previously created from the dropdown
- Multiple channels can be selected
Alarm Name:
- Enter a descriptive name (e.g., "Active Secret Alert")
Description:
- (Optional) Describe what this alarm monitors
Trigger Type: Select when you want to receive notifications
- Active Secret Detected - When a new active credential is found
- Active Public Secret Detected - When active credentials are exposed in public repositories
- Scan Source Verification Failed - When a scan source fails to authenticate
- Incident Created - When a security incident is created in Cremit
4. Click Create Alarm to save
Verification
To verify the integration is working:
- Check that your Slack channel appears in the Channel tab with "Enabled" status
- Verify your alarm rules are listed in the Alarms tab
- Use the Preview tab when creating an alarm to see what the notification will look like
Managing Alarms
View Alarm History:
- Navigate to the Alarm Log tab to see all triggered alarms
- Filter by type, status, or time range
Edit Alarms:
- Click on any alarm in the Alarms tab to modify its settings
- Change channels, trigger types, or other configurations
Disable/Enable Alarms:
- Toggle alarms on or off without deleting them
Troubleshooting
Issue: No channels available when creating alarm
- Message displayed: "No enabled channels available"
- Solution: First create and authorize at least one Slack channel in the Channel tab
Issue: Not receiving notifications
- Alarm is created but Slack messages are not being sent
- Solution: Check that the Channel tab shows your Slack channel as "Enabled", Verify that the alarm is active (not disabled), Test by manually triggering an event that matches the alarm conditions
Notification Types
Cremit sends different types of notifications based on trigger types:
Active Secret Detected:
- Severity level (Critical, High, Medium, Low)
- Secret type (API key, token, password, etc.)
- Location (repository, file path)
- Detection timestamp
- Quick action buttons
Scan Source Verification Failed:
- Scan source name
- Failure reason
- Last successful scan timestamp
- Quick link to configuration
Best Practices
- ✅ Create separate channels for different severity levels (e.g., #security-critical, #security-info)
- ✅ Use descriptive alarm names that quickly identify their purpose
- ✅ Set up multiple trigger types on a single channel for comprehensive coverage
- ✅ Test your alarms after setup using the Preview feature
Key Benefits
- ✅ Instant Alerts: Real-time notifications when security events occur
- ✅ Team Collaboration: Alerts go directly to your team's communication hub
- ✅ Flexible Setup: Choose between OAuth app or webhook
- ✅ Multiple Trigger Types: Monitor various security events from a single integration