Integrations Overview
Overview
Section titled “Overview”Fencer connects to your existing tools and infrastructure through a rich integrations system. Each integration brings security data into one place — letting you scan code repositories, monitor cloud infrastructure, ingest audit logs, track compliance, sync identities, and route alerts to the tools your team already uses. Admin > Integrations is your central hub for connecting, monitoring, and managing all of these connections.
Prerequisites
Section titled “Prerequisites”- To open Admin > Integrations, you need a role that can view integrations, such as the built-in Administrator role.
- Connecting, editing and removing integrations takes the Administrator role.
- An active subscription. When your trial or subscription has expired, cards show Subscribe instead of connecting.
- Some integrations require a paid plan: the security monitoring (SIEM) log sources and the GRC integrations. On a plan without them, their cards show Upgrade.
- Certain integrations depend on another integration being connected first — the card tells you which one is missing.
How it works
Section titled “How it works”Every integration in the catalog has a type, a set of features, and a connection method. When you connect one, Fencer adds a connection to your organization that links it to that service. Each connection tracks its health and shows a status badge: Healthy, Needs attention (it works, but something such as a missing permission needs fixing), or Issue (it has stopped working, for example because credentials expired or access was revoked).
A single service (such as AWS) may offer multiple integrations — for example, one for infrastructure scanning and another for CloudTrail log monitoring. Some integrations connect via OAuth, others through API keys or credential forms. The connection flow varies by provider, but the management experience is consistent across all of them.
Integration catalog
Section titled “Integration catalog”The catalog groups integrations by type. The card names below are the ones shown in Admin > Integrations.
Scanning
Section titled “Scanning”| Card | Guide |
|---|---|
| GitHub (Code) | GitHub Integration |
| GitLab (Code) | GitLab Integration |
| Bitbucket (Code) | Bitbucket Integration |
| Azure DevOps (Code) | Azure DevOps Integration |
| Cursor Origin (Code) | Cursor Origin Integration |
| Git (Code) | Generic Git Integration |
| AWS - Amazon Web Services (Scan) | AWS Integration |
| GCP - Google Cloud Platform (Scan) | GCP Integration |
| Azure | Azure Integration |
| Cloudflare | Cloudflare Integration |
| DigitalOcean, Heroku, Railway, Render, Supabase, Vercel | Hosting Platforms |
| Container Registry | OCI Registry Integration |
| Google Workspace | Google Workspace |
| Microsoft Entra | Microsoft Entra |
| Iru (Kandji) | Iru (Kandji) Integration |
| Zoom | Zoom Integration |
| Notion | Notion Integration |
| Calendly | Calendly Integration |
| Fathom | Fathom Integration |
| Anthropic, OpenAI | AI Integrations |
| Sentry, PostHog, New Relic | Observability |
| Apple Business, Ashby, Attio, MailerSend, Prefect, Schematic | Identity Sources |
Monitoring
Section titled “Monitoring”These integrations send logs to Security Monitoring and need a plan that includes it.
| Card | Guide |
|---|---|
| GitHub (Monitor) | GitHub Integration |
| AWS - Amazon Web Services (Monitor) | AWS Integration |
| GCP - Google Cloud Platform (Monitor) | GCP Integration |
| Google Workspace (Monitor) | Google Workspace |
| GitLab (Monitor) | GitLab Integration |
| Cloudflare (Monitor) | Cloudflare Integration |
| Heroku (Monitor), DigitalOcean (Monitor) | Hosting Platforms |
| 1Password | 1Password Integration |
GRC, notifications and workflow
Section titled “GRC, notifications and workflow”| Card | Type | Guide |
|---|---|---|
| Vanta, Drata, SecureFrame | GRC | Compliance Integrations |
| Slack | Notification | Slack Integration |
| Jira | Workflow | Jira Integration |
| Linear | Workflow | Linear Integration |
Integrations in limited availability
Section titled “Integrations in limited availability”These integrations are being rolled out gradually and appear in the catalog only for organizations that have them enabled. Contact Fencer support if you need one: Snowflake, Rippling, Azure (Monitor), Custom Source and AWS Monitor (Streaming) (AWS streaming monitor).
Fencer also offers an MCP server for AI agents. It is not a catalog card: you connect to it from your AI client.
Usage / Configuration
Section titled “Usage / Configuration”Browsing available integrations
Section titled “Browsing available integrations”- Go to Admin > Integrations.
- Use the tabs to show All, Active (already connected) or Available (ready to connect) integrations. Connected integrations are listed under Active Integrations and the rest under Available Integrations.
- Use the two dropdowns to narrow the list:
- Integration type: Scanning, Monitoring, GRC, Notifications, Workflow
- Application feature: Security Monitoring, Infrastructure Scanning, Architecture, Code Scanning, Container Scanning, Network Scanning, Compliance, Notifications, Workflow, Endpoint Scanning, Identity, Identity Provider, SaaS Scanning
- Use Search integrations… to find an integration by name, or a connection by its account name.
Connecting an integration
Section titled “Connecting an integration”- Find the integration under Available Integrations and click its card.
- Read the Getting Started page, which lists the integration’s features, and click Continue.
- Follow the provider-specific setup, with the setup guide beside the form:
- App installations (GitHub) open the provider in a popup so you can install the Fencer app on your organization.
- OAuth-based integrations (GitLab, Slack, Jira, Linear, Google Workspace, etc.) redirect you to the provider to authorize Fencer.
- API key integrations (Cloudflare, Render, 1Password, Anthropic, OpenAI, etc.) present a form where you enter your credentials.
- Cloud provider integrations (AWS, GCP, Azure) have multi-step configuration wizards for IAM roles, service accounts, or subscription setup.
- Once connected, the integration appears under Active Integrations with a status badge.
Managing active integrations
Section titled “Managing active integrations”Each connection’s card shows the account name and status. From the card you can:
- Edit (the pencil icon) the connection to update credentials or settings, where the integration has any.
- Reconnect (the refresh icon) an OAuth integration to authorize Fencer again.
- Remove (the trash icon) the connection from your organization, after confirming.
- Add new connection (the plus icon) for integrations that allow more than one connection.
An integration with several connections shows one card; click it to expand the list of connections. If a connection shows Issue or Needs attention, check the message on the card for guidance on re-authenticating or fixing permissions.
Integration dependencies
Section titled “Integration dependencies”Some integrations require another integration to be connected first. For example, GitHub (Monitor) requires GitHub (Code). Until the prerequisite is connected, the card cannot be opened and its tooltip names what is missing, for example “GitHub (Code) must be installed first”.
Examples
Section titled “Examples”Connecting GitHub for code scanning
Section titled “Connecting GitHub for code scanning”- Go to Admin > Integrations.
- Click the GitHub (Code) card in the available integrations list, then Continue.
- Click Connect — a popup opens to install the Fencer GitHub App.
- Select the GitHub organization and the repositories you want to grant access to, and click Install.
- You are returned to Fencer’s repository settings. Add the repositories you want to scan.
- Your repositories now appear under Posture > Code.
Connecting Slack for notifications
Section titled “Connecting Slack for notifications”- Go to Admin > Integrations.
- Click the Slack card in the available integrations list, then Continue.
- Click Connect Slack and authorize the Fencer app in your Slack workspace via OAuth.
- Once connected, add a Slack channel or Slack DM destination to your notification rules under Settings > Notifications. See Slack Integration.
Troubleshooting
Section titled “Troubleshooting”- Integration shows “Issue” status: Credentials may have expired or permissions were revoked. Check the message on the card, then reconnect or update the API key.
- ”… must be installed first”: Connect the prerequisite integration first. The tooltip lists exactly which integrations you need.
- Card shows “Upgrade”: The integration is part of a paid feature (security monitoring sources, GRC integrations). Check your subscription plan under Admin > Billing, on the Plans tab.
- Integration not appearing: It may be in limited availability (see above). Contact Fencer support.
- “Must be an administrator to manage integrations.”: Ask someone with the Administrator role to connect or change the integration.
- Cannot remove an integrated vendor: If a vendor was added automatically by an integration, you must disconnect the integration itself rather than removing the vendor record directly.