liquid://methodology

Evidence you can inspect. Limits you can understand.

Liquid Cybersecurity uses scoped, authorized checks and separates observed findings from areas that have not been tested.

01

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.

02

Access and sessions

Declared synthetic roles are compared on named records. Supported checks examine login sessions, access controls and explicitly authorized state changes.

03

Repository and dependencies (early access)

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.

04

Browser tests

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.

05

Severity and remediation

Findings include evidence and correction guidance. AI helps draft instructions grounded in the assessment; human review is required before applying changes.

06

Dated conclusions

The report applies to the stated scope and date. Retests keep their own evidence. No assessment guarantees that a system is free from vulnerabilities.

07

Scope enforced in code

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

Plain-language glossary

The words Liquid uses, in one line each. Canonical terminology rules live in the methodology.

Assessment
A bounded, authorized review of one site. It produces dated evidence, not a guarantee.
Site
The web address you declare as yours. Testing stays inside that declared scope.
Report
The dated record of what was tested, what was found and what stayed untested.
Finding
One observed problem with evidence attached. It is not a guess or a generic tip.
Scope
The exact boundaries of what Liquid may test. Locked before anything runs.
Correction
The change that removes a finding. Only a recorded retest confirms it.
Retest
A new authorized test that checks whether a correction actually worked.
Grade
An optional A to F summary of one signed review. It is dated and goes stale honestly.

Testing requires company authorization. A review or public grade is not a guarantee of security.

Check my website free