Security Swarm
Review and act on findingsWhat’s in a finding
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
On this page
Run your first scan
Review and act on findingsWhat’s in a finding
Act on a finding
Scan profilesCreate a profile
Basic information
Threat model
Investigation guidance
Triage guidance
Sandbox validation
Report
Remediation guidance
Advanced inputs
Ingestion profiles
Organization and enterprise profiles
Interactive mode
Configure sandbox validation
Scale scanningChoose a scan mode
Scan effort
Bulk scan an organization
Ingest existing findings
Auto Scan
Scan new commits
Start scans from Automations
Manage and monitor scansScan history
Change a scan’s profile
Security dashboard
Access and permissions
Compare Security Swarm with another scanner
FAQ
Working with Devin
Security Swarm
Copy pageCopy page
Use Devin Security Swarm to find, triage, and remediate security vulnerabilities across your repositories with code scans and automated fixes
Copy pageCopy page
Security Swarm is Devin’s security scanning and remediation product. It builds a threat model tailored to your code, investigates and validates potential vulnerabilities, and helps you fix findings through pull requests. It can identify vulnerabilities like remote code execution (RCE), SQL injection, path traversal, server-side request forgery (SSRF), authorization bypasses, memory-safety bugs, denial-of-service vulnerabilities, and more. It can even identify chained exploits spanning multiple files. Security Swarm is a custom orchestration of Devins we are calling Agentic MapReduce. It divides your repo among parallel Devins, providing broad coverage and deep investigation while bounding cost, making it cost-effective to scan large codebases. We also benchmarked Security Swarm against a ground-truth set of published vulnerabilities from the GitHub Advisory Database.
Prerequisites
Run your first scan
Open Security in the left sidebar and click Start scan.
Under Single repo, choose a repository to scan.
Optionally select a scan profile and a scan effort. Leaving the profile blank uses Security Swarm’s built-in security scan.
Make sure Interactive mode is enabled.
Click Run Scan.
When the proposed threat model is ready, review it and either click Looks good, start scanning or provide feedback.
As findings appear, review the evidence and act on the findings that need attention.
The New Scan sheet offers other scan modes for scanning several repositories at once or importing findings from an existing scanner.
Creating a scan profile, running an interactive scan, and reviewing the findings in Security Swarm
For repeatable scans, create a profile that captures your scope, threat model, severity criteria, validation steps, and remediation constraints.
Review and act on findings
Open a scan to see its findings. The page displays a list of findings on the left, grouped by severity, and the selected finding’s details on the right. The status tabs show a live count:
Open — needs attention.
Reviewed — has been reviewed and no longer requires action.
Dismissed — was determined as a false positive or duplicate.
While a scan is running, the page updates automatically as findings arrive.
Reviewed is a workflow status, not confirmation that a fix was merged. A finding can be marked Reviewed manually or when a later scan determines that it is no longer present.
What’s in a finding
A finding includes:
Severity, status, exploitability, confidence, and category.
The affected file path and code snippets.
A description of the issue and a remediation recommendation.
A sandbox validation result, supporting evidence, and validation artifacts.
Associated pull requests and their open, merged, or closed state.
Code owners and notes, when available.
Treat a risky code pattern as a lead, not proof of a vulnerability. Check that the finding traces a reachable path from attacker-controlled input, accounts for validation and authorization controls, and explains a concrete security impact.
Act on a finding
Assign to Devin
Feedback
Adjust
Status menu
Starts a Devin session to remediate the issue and open a pull request. The session and resulting pull request are tracked on the finding.
Sends context to a feedback session that refines the scan profile for future scans. For example, explain that a reported data flow is protected by an internal gateway so future scans can account for that control.
Overrides the finding’s severity, with optional context for Devin. For example, lower the severity when exploitation requires privileged internal access, and include that constraint as context.
Marks the finding as Open, Reviewed, or Dismissed. Keep a finding Open while it needs action, mark it Reviewed after triage, or dismiss it when it is a false positive or duplicate.
Scan profiles
A scan profile controls the scan’s scope and provides guidance for each stage of the scan. Every scan can use one profile. To evaluate a repository against multiple attacker personas or threat categories, run separate scans with different profiles.
A specific threat model is one of the most effective ways to keep coverage consistent across scans. Define the attacker, sensitive assets, trust boundaries, important entry points, and explicit exclusions.
Manage profiles from the Profiles tab on the Security page.
Create a profile
You can create a profile in two ways:
Generate with Devin — describe the application, threats, scope, exclusions, and severity standards in natural language. Devin drafts the profile for you.
Create manually — fill in each profile input yourself.
Generating with Devin is a useful starting point, but review every generated field before using the profile. Leaving an optional guidance field blank applies Security Swarm’s built-in behavior for that stage.
Basic information
Profile name — name the application surface or threat category, rather than the team running the scan. Example: Multi-tenant API authorization.
Description — summarize the profile’s scope and security objective. Example: Find authentication, authorization, and tenant-isolation vulnerabilities in the public API.
The examples below combine into a single profile for a multi-tenant API. Adapt the boundaries, commands, and severity standards to your application.
Threat model
Describe the attacker, sensitive assets, trust boundaries, important entry points, and anything explicitly out of scope. This guidance shapes the rules Devin generates before investigation begins.
Assume an unauthenticated internet attacker or an authenticated user in one tenant. Focus on public HTTP handlers, OAuth callbacks, API tokens, administrative actions, and accesses to tenant-owned data. Treat internal development scripts and local-only tools as out of scope. Prioritize authentication bypasses, cross-tenant access, token leakage, injection, and SSRF.
Investigation guidance
Define how Devin should investigate a potential issue and what evidence it should collect. Ask it to account for existing mitigations and to distinguish reachable vulnerabilities from theoretical concerns.
Trace untrusted input from the route through middleware and service layers to the sensitive operation. Check authentication, authorization, tenant scoping, validation, and escaping at every boundary. Identify the exact reachable path and cite the relevant files and lines. Do not report a theoretical issue when an effective mitigation blocks the path.
Triage guidance
Define how Devin should deduplicate and prioritize findings. Include your severity criteria so results match your organization’s standards.
Group findings that share the same root cause. Treat unauthenticated remote code execution and cross-tenant write access as critical. Treat cross-tenant read access and credential disclosure as high. Treat single-user availability issues as medium unless they can affect shared infrastructure. Label defense-in-depth recommendations as low.
Sandbox validation
Enable sandbox validation when Devin can safely build and exercise the application. Explain how to start the application, create test data, authenticate, and demonstrate the expected security boundary. Use Validate severities to choose the lowest severity that Devin validates in a sandbox. Only findings at or above that severity start a validation session; by default, critical, high, and medium findings are validated. Raise the threshold to critical or high to spend validation effort only on the findings that matter most.
Use the repository's documented development setup. Start the API and create two non-production tenants with one test user in each. Attempt the suspected request as a user from the other tenant, then verify both the HTTP response and persisted data. Do not call production services or modify production data.
An unsuccessful validation does not always disprove a finding. Review the validation result and artifacts to determine whether an effective mitigation blocked the exploit or the configured environment prevented Devin from completing the test.
Sandbox validation starts a separate Devin session for each finding. See Configure sandbox validation for environment guidance.
Report
Enable reports when you need a summary artifact after the scan. Specify the intended audience and the information the report should emphasize.
Write an executive summary for security and engineering leads. List confirmed critical and high findings first, followed by unvalidated findings. Include affected components, validation status, pull request status, and a prioritized remediation plan.
Remediation guidance
Specify constraints that Devin should follow when you assign a finding for remediation. Include testing expectations, compatibility requirements, and practices to avoid.
Prefer the smallest safe change and preserve existing public API behavior. Add a regression test that fails before the fix and passes afterward. Run the affected package's lint and test commands. Avoid major dependency upgrades unless the vulnerability cannot be fixed safely without one.
Advanced inputs
Open Advanced to control file scope and investigation batches:
Include globs — restrict the scan to matching files. For example, apps/api/** and packages/auth/**.
Exclude globs — remove irrelevant files from the selected scope. For example, /generated/, /vendor/, and /fixtures/.
Batch size — control how many files with signals are grouped into each investigation batch. Leave this at its default unless you are deliberately tuning scan behavior. The accepted range is 1–500; the default is 5.
Overly broad exclusions can hide vulnerable code or remove context needed to understand a data flow. Exclude only files you are confident are irrelevant to the profile.
Ingestion profiles
A profile’s mode is fixed when you create it. Discover profiles (the default) analyze your code to find new issues and use the guidance fields above. Ingest profiles import findings you already have from another scanner or report, and replace the scope and threat model inputs with two guidance fields:
Ingestion source — where the existing findings live and how Devin should fetch them. For example, fetch open alerts from GitHub code scanning through its REST API, or read a Semgrep report committed at reports/semgrep.json. Reference credentials by organization secret name rather than pasting a token.
Post-ingestion triage — how Devin should triage the imported findings: what to dismiss, what to reprioritize, and what to treat as a duplicate. For example, dismiss findings in test fixtures and treat findings with the same rule ID and file as duplicates.
See Ingest existing findings for how to run a scan with an ingestion profile. The Profiles tab can be filtered by scan type and by mode (Discover or Ingest).
Organization and enterprise profiles
New profiles are organization-scoped. Enterprise admins can later change a profile’s visibility to Enterprise, making it available across
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。