Demonstration topics
- Audit setup and scope
- Technical health scoring
- Findings and prioritization
- Agency workspaces
- Reports and exports
- Verification
Prepare a useful request
- Identify the website, organization, and person responsible for approving access or work.
- Describe the objective, current evidence, deadline, affected users, and known constraints.
- State the number of websites, environments, users, clients, or reports involved when asking about a plan or implementation.
- Do not send passwords, private keys, payment-card data, health information, or unnecessary personal information through the public form.
What happens after submission
- 01
Request review
The request is checked for scope, contact information, authorization context, and the appropriate commercial or support path.
- 02
Clarification
Asuruas may request the minimum additional information needed to understand the website, workflow, volume, or risk.
- 03
Next action
A qualified request may lead to a discovery call, service review, audit scope, plan recommendation, security response, or written referral.
- 04
Record retention
The request is retained according to the applicable privacy and data-retention policy and should not contain unnecessary secrets.
Decision and verification record
Scope
Name the website, environment, URLs, entities, templates, or user journeys included in the request an asuruas demonstration decision.
Decision
Record the chosen action, owner, priority, dependencies, approval, and the evidence that justified it.
Verification
Confirm the report matches the current source records, scope, approvals, and verification status before distribution.