Generated fixes that weaken another boundary
A change that resolves a visible error can also broaden CORS, disable cookie protections or move a server operation into client code.
Security for Windsurf-built apps
A security feedback loop for Windsurf projects
Pair external observations from the deployed app with optional connected-source signals. BoringSec identifies which scanner produced each result and whether the evidence is verified, partial or unavailable.
Run the loop after agent-generated changes to authentication, APIs, dependencies, environment handling or database access.
Run scans only on systems you own or are authorized to assess. Deep engines require verified authorization and may remain unavailable for a target.
report / sample findingIllustrative
High
Example report structure
Secure flag explicitly disabled on an auth cookie
- Evidence
- Connected source analysis identifies cookie configuration that sets Secure to false in an authentication-related context.
- What it means
- The source signal may allow the cookie to travel over an unencrypted connection and must be reviewed against environment-specific configuration.
- Fix and verify
- Enable Secure in production, keep HttpOnly and an appropriate SameSite policy, deploy, then verify the actual Set-Cookie response.
This is an illustrative finding, not a result for your application. Live reports show the scanner, evidence state and coverage limits for the actual target.
Common risk paths
What deserves a closer look
These are risk patterns relevant to Windsurf projects—not claims that every project has them. A finding appears only when a scanner returns supporting evidence.
Secrets embedded in source or bundles
Agentic edits can reuse examples or environment values in places that become committed or shipped to the browser.
Auth and ownership logic drifting apart
New routes and data models need the same server-side authorization rules as the original application.
Honest coverage
What each scan surface can prove
URL evidence, connected source and authorized deep engines answer different questions. BoringSec keeps those sources separate and shows partial, blocked and unavailable states instead of turning an untested surface into a pass.
Read the public methodologyDeployed web surface
Checks the public response path for TLS, security headers, DNS and email authentication, cookies, CORS, exposed files, technology signals and other externally observable controls.
Shipped JavaScript
Inspects bounded, same-origin frontend bundles for secret-shaped values and records partial coverage when an asset cannot be fetched or exceeds a safety limit.
Independent deep engines
Nuclei, OWASP ZAP and Medusa continue asynchronously only when the requested scan is authorized and the engine is available. Their running, blocked or unavailable state stays visible.
Repository context
A separately connected repository can add source-level evidence for committed secrets, auth and database risk patterns, dependency advisories and server/client boundary mistakes.
From observation to verification
A report built for the next action
- 01
Observe
Inspect the public response path and start eligible background engines.
- 02
Verify evidence
See what was observed, by which scanner and with what confidence.
- 03
Fix in context
Use a concrete remediation path and the Windsurf-relevant context.
- 04
Retest
Run a fresh assessment; monitoring can detect later regressions separately.
Questions before you scan
Does BoringSec need access to my Windsurf account?
No. A live scan starts from the deployed URL and observes only the public surface. Repository access is a separate, explicit connection and is not required for the URL scan.
What can a URL-only scan prove?
It can support findings with externally observable evidence such as response headers, TLS behavior, public files, shipped bundles and bounded backend probes. It cannot prove that private source code or authenticated workflows are safe.
Does a good score mean the application is completely secure?
No automated scan can prove complete security. BoringSec reports assessed, partial, unavailable and authorization-required coverage explicitly so a clean result is not presented as evidence for surfaces that were never tested.
Is BoringSec affiliated with Windsurf?
No. BoringSec is an independent security service and is not sponsored by, endorsed by or affiliated with Windsurf.
Check the deployed application, then verify every fix
Start with the public URL. Add source or authenticated context only when you choose to expand coverage.
Start a security scan