llms.txt
Compare with other sites' llms.txt files →# Borg
> Borg is autonomous application security: continuous pentesting that chains vulnerabilities and tests business logic the way a real attacker would, then pushes confirmed findings straight into Linear, Jira, and GitHub. Odin is the platform; Whitebox Pentest runs application pentests, Attack Surface Monitoring tracks exposed assets, and PR Security Reviews check pull requests.
## Product
- [Platform](https://www.borghq.io/platform): How Odin, whitebox pentesting, attack surface monitoring, and PR security reviews discover assets, find vulnerabilities, and confirm them.
- [Enterprise](https://www.borghq.io/enterprise): Odin's modular approach, the embedded research service, deployment and scale.
## Company
- [About](https://www.borghq.io/about): Who Borg is and how the company got here.
- [Contact](https://www.borghq.io/contact): Get in touch or book a demo.
- [Privacy Policy](https://www.borghq.io/privacy): How Borg handles data.
## Blog
- [Blog index](https://www.borghq.io/blog): All articles.
- [Preview Environment Security Testing: Authenticated Checks](https://www.borghq.io/blog/preview-environment-security-testing-authenticated-checks): How to run authenticated security tests against ephemeral PR preview environments without leaking secrets, touching real tenants, or trusting a silently failed login.
- [Security Regression Testing for Authorisation Fixes](https://www.borghq.io/blog/security-regression-testing-for-authorisation-fixes): How to turn one confirmed authorisation bug into a durable security regression test: positive and negative assertions, role and tenant matrix, isolated fixtures, CI ownership.
- [Pentest as a Service Compared: Five PTaaS Delivery Models](https://www.borghq.io/blog/pentest-as-a-service-compared-five-ptaas-delivery-models): Pentest as a service is a delivery wrapper, not a test method. Compare five PTaaS models by who tests, context, validation, cadence and retesting.
- [The Part of Crypto Security Nobody Talks About](https://www.borghq.io/blog/the-part-of-crypto-security-nobody-talks-about): Much of crypto runs on ordinary web software. Here are two vulnerabilities we found in the Solana Foundation's tokens.xyz, an account aliasing bug and same-origin XSS, and how they were fixed.
- [API Security Testing Tools Compared: What Each One Checks](https://www.borghq.io/blog/api-security-testing-tools-compared-what-each-one-checks): API security testing tools compared by what each checks: scanners, fuzzers, manual proxy testing, monitoring and code-aware testing, and where BOLA bugs slip through.
- [IDOR Testing for APIs: How to Find Broken Object Access](https://www.borghq.io/blog/idor-testing-for-apis-how-to-find-broken-object-access): IDOR testing for APIs, done as an authorisation check on every object reference. Two-account setup, every operation, and how to make it repeatable per release.
- [Manual Pentest vs AI Pentest: What Each Finds and Where Humans Win](https://www.borghq.io/blog/manual-pentest-vs-ai-pentest-what-each-finds-and-where-humans-win): Comparing manual pentest vs AI pentest? See what each method finds in auth, APIs, and logic, where human testers win, and how Borg verifies code changes.
- [PHP2Shell CVE-2026-109618: What to Do Right Now](https://www.borghq.io/blog/php2shell-cve-2026-109618-what-to-do-right-now): Facing PHP2Shell CVE-2026-109618? Here is what is verified before the 14:00 UTC patch, what remains unconfirmed, and your patch-day checklist.
- [Tenant Isolation Testing: How to Prove Tenant Boundaries Hold](https://www.borghq.io/blog/tenant-isolation-testing-how-to-prove-tenant-boundaries-hold): Learn how to run tenant isolation testing across APIs, queues, and background workers. Prove one customer cannot access another before shipping to production.
- [PR Security Review Tools Compared: Diff Checks Before Merge](https://www.borghq.io/blog/pr-security-review-tools-compared-diff-checks-before-merge): Compare PR security review tools by how they check diffs: rule-based SAST, AI autofix engines, and context-aware diff review before code hits production.
- [Verified Security Findings: How to Tell Proof From Inference](https://www.borghq.io/blog/verified-security-findings-how-to-tell-proof-from-inference): Verified security findings mean different things to different vendors. How to tell an inferred issue from one an attack actually proved, and what to ask for.
- [What to Do With a Security Finding You Are Not Going to Fix](https://www.borghq.io/blog/accepted-risk-security-finding-what-to-do-if-you-wont-fix): A finding you decide not to fix is still a decision. The difference between a false positive, an accepted risk and not yet, and what each one should record.
- [Security Review for AI-Generated Code: What Changes Before Merge](https://www.borghq.io/blog/security-review-for-ai-generated-code-what-changes-before-merge): More of every pull request is machine-drafted and the bug classes have not changed. What security review must catch in the diff before merge, and what it cannot.
- [Offensive Security Testing in Production: What to Agree First](https://www.borghq.io/blog/offensive-security-testing-in-production-what-to-agree-first): What to settle before offensive testing runs against a live application: scope, timing, rate, permitted actions, and where staging answers a different question.
- [From Pentests to Continuous Security with Pixels](https://www.borghq.io/blog/from-pentests-to-continuous-security-pixels): How Pixels moved from scheduled pentests to continuous security with Borg, covering its live game, authentication, APIs, on-chain rewards, and open-source releases.
- [How to Prioritise Security Findings That Have No CVE](https://www.borghq.io/blog/how-to-prioritise-security-findings-that-have-no-cve): EPSS and KEV cover published CVEs only, and a self-assigned CVSS score loses that shared context. How to rank exploitable findings in your own application code.
- [AI Application Security Testing: The Authorisation Boundary](https://www.borghq.io/blog/ai-application-security-testing-the-authorisation-boundary): OWASP's LLM list names permission-aware retrieval as a requirement and leaves enforcement placement to you. Here is how to test whether the tenant boundary in an AI feature actually holds.
- [Security Testing Every Release Without a Manual Bottleneck](https://www.borghq.io/blog/security-testing-every-release-without-a-manual-bottleneck): Security review is often the last release step that waits on a person. What can run per merge, what still needs a human, and how the two split.
- [Two Years of Continuous Security with Banana Gun](https://www.borghq.io/blog/banana-gun-continuous-security): How Borg has worked alongside Banana Gun for more than two years, providing continuous offensive security as its infrastructure evolved.
- [How Automatic Retests Verify a Fix When Your PR Merges](https://www.borghq.io/blog/how-automatic-retests-verify-a-fix-when-your-pr-merges): Link a pull request to a security finding and the merge triggers verification. How the linking works, what the review reads, the outcomes, and where it stops.
- [How to Continuously Map Your External Attack Surface](https://www.borghq.io/blog/how-to-continuously-map-your-external-attack-surface): Mapping an external attack surface continuously: what counts as an asset, the discovery techniques and why they run on different clocks, and where it stops.
- [Autonomous Pentesting vs Vulnerability Scanning: What Each Finds](https://www.borghq.io/blog/autonomous-pentesting-vs-vulnerability-scanning-what-each-finds): Autonomous pentesting and vulnerability scanning answer different questions. What each one reaches, where each stops, and when to reach for which.
- [SAST and Business Logic Vulnerabilities: What Static Analysis Can Reach](https://www.borghq.io/blog/sast-and-business-logic-vulnerabilities-what-static-analysis-can-reach): Static analysis and business logic are a poor fit by construction. What SAST covers well, what the published accuracy research shows, and what covers the rest.
- [Bug Bounty Alternatives: What AI Security Testing Replaces, and What It Doesn't](https://www.borghq.io/blog/bug-bounty-alternatives-what-ai-security-testing-replaces-and-what-it-doesn-t): Bug bounty alternatives compared for engineering teams: what continuous AI offensive testing genuinely replaces, and where a bounty is still the right instrument.
- [Full Pentest vs PR Security Review: What Each One Actually Answers](https://www.borghq.io/blog/full-pentest-vs-pr-security-review-what-each-one-actually-answers): A full pentest and a PR security review answer different questions. Here is what each one covers, what neither sees, and why you need both.
- [What Is Code-Aware Application Security Testing?](https://www.borghq.io/blog/what-is-code-aware-application-security-testing): Code-aware application security testing uses repository context to drive targeted offensive attacks, finding auth and logic bugs that traditional scanners miss.
- [How to Test Business Logic Vulnerabilities in a SaaS Application](https://www.borghq.io/blog/how-to-test-business-logic-vulnerabilities-in-a-saas-application): Learn how to test business logic vulnerabilities in SaaS using a 5 step offensive methodology. Surface auth, billing, and isolation bugs that scanners miss.
- [What Is Continuous Pentesting? A Definition for Engineering Teams](https://www.borghq.io/blog/what-is-continuous-pentesting-a-definition-for-engineering-teams): What is continuous pentesting? Learn how this offensive security practice replaces annual audits with real-time testing for auth flows, APIs, and business logic.
- [XBOW Alternatives: Comparing Autonomous AI Pentesting Platforms](https://www.borghq.io/blog/xbow-alternatives-comparing-autonomous-ai-pentesting-platforms): XBOW alternatives compared on code context, pull request review, proof of exploitation and pricing: Borg, Hacktron, MindFort, RunSybil, Escape and Aikido.
- [Why we dropped "Security" from our name](https://www.borghq.io/blog/why-we-dropped-security-from-our-name): The story of how bug bounties in a living room turned into Borg, and why everything we've built now lives under one name.
- [Your scanner didn't find it. Mjolnir did.](https://www.borghq.io/blog/your-scanner-didnt-find-it-mjolnir-did): Scanners match known patterns. Mjolnir reads your code, tests the auth and business logic behind it, and returns findings with a working proof of concept.
- [What startups get wrong about Application Security](https://www.borghq.io/blog/what-startups-get-wrong-about-application-security): Most startups treat security as a compliance checkbox. Here's why that approach fails and what a practical appsec strategy actually looks like when you're shipping fast.
- [How Borg pushes findings to Linear, Jira, and GitHub automatically](https://www.borghq.io/blog/how-borg-pushes-findings-to-linear-jira-github): Pentest findings only get fixed once they are tickets. How to connect Linear, Jira or GitHub to Odin, set auto-ticketing, and verify the fix afterwards.
- [Your Vulnerabilities exist right now. Odin finds them first.](https://www.borghq.io/blog/your-vulnerabilities-exist-right-now-odin-finds-them-first): Your attack surface changes with every deployment. Odin provides continuous discovery, automated testing, and daily reporting so nothing slips through the cracks.