FrontierCyber Defence

Our own target

How our scan scores against holes we planted

Updated 8 November 2026

The figures on our main page come from published research. This page is our own measurement. We stood up a target we own, planted a known set of holes in it, and scan it on a schedule with the same pipeline a customer gets. The scorecard below shows what the scan found and, at the top, the holes we planted and did not find.

The proving ground scorecard

2 of the 11 holes we planted were missed on this run, and 9 were found.

  1. PG-009missed
  2. PG-010missed
  3. PG-001found
  4. PG-002found
  5. PG-003found
  6. PG-004found
  7. PG-005found
  8. PG-006found
  9. PG-007found
  10. PG-008found
  11. PG-011found

Our scan of proving.synchronality.com, run 8 November 2026, by scanner build 04abbed. Every finding on this run maps to a hole we planted.

The holes we missed

These holes are planted in the target and this run did not find them. We list them first.

  • cross-site scripting /guestbook

    Stored comments render unescaped, so a stored comment can carry a script. We planted this to measure stored scripting, which the current probes do not submit. It stays on the scorecard as a miss until our scan finds it.

  • access control /api/profile?id=

    Any user's record is returned by id with no authentication, an insecure direct object reference. We planted this to measure access control between accounts. A scan without a test account cannot see it, and it stays a miss until this scorecard runs with one.

How this is scored

  1. This target is a server we own and control, and every hole in it is planted on purpose.
  2. We scan it with the same probe code a customer scan runs, with no special case for our own site.
  3. This scorecard does not run the signature stage, where our known-vulnerability inferences live, so a false alarm there would not show on this page. We check that stage separately, by scoring a full customer scan of this same target.
  4. The answer key is kept with our code. It lists every planted hole, its category, its location, and how it was planted.
  5. The scoring compares the scan's findings to that answer key. A planted hole with a matching finding is found. A planted hole with no matching finding is a miss, and the miss count is at the top of this page.
  6. The proving ground runs on its own hourly budget and its own schedule. It shares no budget and no data path with any customer scan.
Every hole planted in the target, with where it is and whether the scan found it
IDCategoryLocationSeverityResult
PG-001 security headers response headers on every page Low Found
PG-002 cookie flags Set-Cookie on / Low Found
PG-003 published versions Server and X-Powered-By response headers Low Found
PG-004 cross-site scripting /search?q= High Found
PG-005 open redirect /?url= Medium Found
PG-006 sensitive file exposure /.git/config High Found
PG-007 sensitive file exposure /backup.sql High Found
PG-008 sensitive file exposure /administrator/ Medium Found
PG-011 cross-site request forgery /guestbook Medium Found
PG-009 cross-site scripting /guestbook High Missed
PG-010 access control /api/profile?id= High Missed

The target is deliberately vulnerable and holds no real data. The answer key it is scored against is kept with our code, and every number on this page is computed from it.