Public surface
Authorized HTTPS reads examine security headers, TLS certificate dates, CAA, security.txt and redirects. A limited surface review is not a complete penetration test.
liquid://methodology
Liquid Cybersecurity uses scoped, authorized checks and separates observed findings from areas that have not been tested.
Authorized HTTPS reads examine security headers, TLS certificate dates, CAA, security.txt and redirects. A limited surface review is not a complete penetration test.
Declared synthetic roles are compared on named records. Supported checks examine login sessions, access controls and explicitly authorized state changes.
In early access: it has not yet run for customers. A declared revision is reviewed for supported patterns and published OSV advisories for identified versions. Unrecognized packages and unavailable evidence are marked as gaps.
Bounded Chromium tests can verify supported login cookies, JavaScript runtime versions and a declared CSRF fixture. This requires the isolated worker to be deployed and accepted; untested flows remain untested.
Findings include evidence and correction guidance. AI helps draft instructions grounded in the assessment; human review is required before applying changes.
The report applies to the stated scope and date. Retests keep their own evidence. No assessment guarantees that a system is free from vulnerabilities.
For authorization-gated assessments, target requests are checked in server code against the signed origin, method, port and paths. Requests outside that scope are refused. Public free checks have their own limited scope and consent. Paid work starts only after the required approval and checks; leaving the page does not cancel an already saved request.
See what an assessment looks like: illustrative terminal replay with synthetic data
The words Liquid uses, in one line each. Canonical terminology rules live in the methodology.
Testing requires company authorization. A review or public grade is not a guarantee of security.
Check my website free