Platform Overview

Overview

Fencer is a unified security platform that helps you discover, monitor, and remediate vulnerabilities across your entire technology stack. It brings together code scanning, cloud infrastructure assessment, SIEM-based security monitoring, identity management, and more into a single pane of glass. Everything in Fencer is scoped to an Organization, which acts as your team’s workspace and security boundary.

How it works

Fencer connects to your existing tools and infrastructure through integrations. Once connected, it continuously scans your assets — repositories, cloud accounts, domains, endpoints, containers, and SaaS applications — and surfaces security findings as vulnerabilities or detections. You triage, assign, and resolve these findings directly within Fencer, or push them to external ticketing systems like Jira or Linear.

The platform is organized into four main navigation sections, each grouping related capabilities together. Within an organization, all URLs follow the pattern /a/<organization-slug>/..., keeping your data isolated and context clear.

Key capabilities

Vulnerability management

The central hub for all security findings. Vulnerabilities flow in from every scanner type and are grouped, prioritized by severity, and tracked through a lifecycle of statuses (Open, Ready for verification, Resolved). You can assign vulnerabilities to team members, add comments, and perform bulk operations.

Scanning modules

Fencer provides scanning across multiple surface areas, each with its own page under Posture:

1. Infrastructure — Cloud configuration auditing for AWS, Azure, GCP, Cloudflare, 1Password, and hosting platforms (Heroku, Render, Vercel, Railway, DigitalOcean, Supabase).
2. SaaS — Security checks for connected SaaS accounts (Google Workspace, Microsoft Entra, Zoom, and GitHub).
3. Code — Static analysis of your repositories’ source code.
4. Secrets — Detection of exposed API keys, passwords, tokens, and credentials in your codebase.
5. Artifacts — Container image and OCI artifact vulnerability scanning.
6. Dependencies — Identification of known vulnerabilities in third-party packages.
7. Domains — DNS, SSL, DMARC/SPF/DKIM checks, subdomain discovery, and phishing detection.
8. Network — Discovery and assessment of the network services your cloud accounts and domains expose.
9. Application — Runtime web application scanning.
10. Endpoint — Device security posture assessment via MDM integration.
11. Penetration Testing — AI penetration tests, and findings imported from manual tests.

Security monitoring (SIEM)

The Operations section provides a SIEM that ingests security events from connected sources such as AWS (CloudTrail and more), Google Cloud, GitHub, GitLab, Google Workspace, Cloudflare, and 1Password. Detection rules run against these events to produce security detections, which you investigate and resolve under Operations > Security Monitoring.

Threat hunting

Operations > Threat Hunting lets you proactively explore raw security events across all connected log sources using OCSF-normalized events, enabling ad-hoc investigation and incident analysis.

Identity management

Track organization and vendor identities synced from providers like Google Workspace, Microsoft Entra, and 1Password, and run access reviews over them.

Product navigation

When you log into Fencer and select an organization, the sidebar organizes features into these sections:

• Main — Home, Vulnerabilities, Advisory, Assets, and Agents.
• Posture — All scanning modules: Infrastructure, SaaS, Code, Secrets, Artifacts, Dependencies, Domains, Network, Application, Endpoint, Identities, and Penetration Testing.
• Operations — Threat Intelligence, Threat Hunting, Security Monitoring, and Network Flows.
• Admin — Integrations, Vendor Catalog, Settings, Team, and Billing (visible to roles that can view organization settings, such as Administrator).

Each link appears only to roles that can open its page. See Navigation and Layout for what each link covers.

Note

Most Posture pages, Agents, and the Threat Hunting, Security Monitoring, and Network Flows pages are paid capabilities. When your plan does not include one, its link still appears in the sidebar, dimmed and marked with a lock icon.

Integrations

Fencer connects to a wide range of third-party services:

• Source control — GitHub, GitLab, Bitbucket, Azure DevOps, Cursor Origin, and any Git repository
• Cloud and hosting — AWS, Azure, GCP, Cloudflare, DigitalOcean, Heroku, Render, Railway, Vercel, Supabase
• Container registries — OCI-compatible registries
• Endpoint management — Iru (Kandji)
• Security monitoring — AWS, GCP, GitHub, GitLab, Google Workspace, Cloudflare, Heroku, DigitalOcean, 1Password
• Identity — Google Workspace, Microsoft Entra, 1Password, and member sync from tools such as Anthropic, OpenAI, Notion, Zoom, Calendly, Sentry, and PostHog
• Compliance — Drata, Vanta, SecureFrame
• Notifications — Slack
• Workflow and ticketing — Jira, Linear

See the Integrations Overview for the full catalog.

Examples

A typical workflow in Fencer looks like this:

1. Connect your GitHub organization from Admin > Integrations.
2. Fencer discovers your repositories and runs code scans automatically.
3. Findings appear on the Vulnerabilities page.
4. You assign critical findings to team members and track progress through status changes.
5. Optionally, push findings to Jira or Linear for external tracking.

Related pages

• Quickstart Guide
• Navigation and Layout
• Roles and Permissions