Secure design
The public enquiry flow avoids storing message content in a dedicated website database and asks users not to submit sensitive material.
Security
A concise public statement of secure defaults, reporting routes and proportionate assurance.
Request a scoping callWho this helps
Useful when
The position
Pegasus applies data minimisation, controlled change and a dedicated disclosure route to the website. Public statements are deliberately proportionate: no website is represented as vulnerability-free, and detailed security information is shared only where authority and need are established.
A defined scope and accountable decision owners
Controls matched to the real operating context
Evidence that can be reviewed, tested and improved
Scope
Every engagement is scoped around authority, operating context, available evidence and the decision that must be made.
The public enquiry flow avoids storing message content in a dedicated website database and asks users not to submit sensitive material.
Dependencies, hosting behaviour and material changes are reviewed through the release process, with defects corrected before checkpointing where practicable.
Suspected vulnerabilities should follow the responsible-disclosure route so evidence, safety and communications can be controlled.
Questions answered
No. It explains the current design approach and reporting route; it is not a guarantee of zero vulnerabilities or uninterrupted availability.
Use the responsible-disclosure page and send only the minimum non-destructive information needed for initial triage.
Start the conversation
A first conversation is used to understand context, authority and the decision required—not to force a predetermined package.
Request a scoping call