Home / Methodology

Methodology

How Svitsec delivers security testing.

A methodology explains planning and approval, what gets tested, and how findings are validated. The report still needs to hold up.

Written boundariesManual validationEvidence quality
Methodology and evidence interface
Approved before testing.Boundaries, access expectations, timing, and communication plans are confirmed before work begins.

Defined boundaries

Testing starts with boundaries, access expectations, target systems, exclusions, constraints, and the people who will use the result.

Manual validation

Tools broaden the review, but material findings are confirmed manually so the output reflects real exposure, not scanner noise.

Evidence quality

Findings explain the observed issues, which roles or systems are affected, and what to change next.

Follow-up and handoff

Reports are written for engineering, security, leadership, procurement, and customer-facing teams.

Service line depth

Each service line needs different depth, but the operating standard stays consistent.

The work changes by service line. Expectations stay the same: boundaries, manual validation, and evidence.

  • Applications: authentication, authorisation, tenant boundaries, APIs, mobile trust, and workflow abuse
  • Infrastructure: exposure, remote access, cloud identity, management paths, segmentation, and reachability
  • Posture: governance, identity, resilience, evidence expectations, and uplift priorities
  • AI: data access, retrieval leakage, tool permissions, approvals, logging, and automation boundaries

References

Use frameworks where they help.

The work can align with OWASP, cloud and identity guidance, the Essential Eight, or NIST-style controls.

Keep the evidence actionable.

AI review follows the same rule: prompts are one input. Permissions, retrieval boundaries, tool access, approvals, logging, and workflow shape the result.

Working principle: reduce ambiguity and keep the output actionable.

Request a quote

Request a quote.

Describe the system, timeline, and decision.