Bounded by authorization
Remote scanning is an explicit operator action. The scanner applies URL and DNS policy, redirect destination checks, robots handling and bounded retrieval. It does not recursively crawl a site or execute page JavaScript.
\n \n \n
Searqon handles discovery data and technical evidence. Its security posture must be inspectable, scoped and honest about what has—and has not—been independently verified.
Remote scanning is an explicit operator action. The scanner applies URL and DNS policy, redirect destination checks, robots handling and bounded retrieval. It does not recursively crawl a site or execute page JavaScript.
The repository includes passwordless email authentication, server-side session digests, same-origin write checks, secure production cookie settings and PostgreSQL row-level security for organization-scoped data.
Evidence records and local ledgers support content digests, hash-linked entries and detached Ed25519 checkpoints. The local ledger is not encrypted, WORM storage or distributed multi-writer custody.
The repository runs Node.js 22/24 tests, PostgreSQL integration checks, CodeQL and full-history secret scanning in CI. Dependency and release checks are also part of the pipeline.
Searqon does not claim SOC 2, ISO 27001, a completed independent penetration test or formal OWASP ASVS certification. The OWASP Top 10:2025 and ASVS 5.0 are useful reference frameworks; conformance requires a scoped, evidence-backed verification process.
Independent security testing, privacy and legal review, backup/restore exercises, operational telemetry, incident response, deployment controls and customer acceptance remain required gates.
Use the repository's published security policy for responsible disclosure. Please do not publish sensitive vulnerability details in a public issue.