Cyber Security

Vulnerability Assessment

Scanning infrastructure and applications for known vulnerabilities.

01

Who needs it

Companies needing regular visibility of known weaknesses.

02

Key advantages

  • Broad coverage quickly
  • Known CVEs identified
  • Repeatable on a schedule
03

Core features

  • Network and host scanning
  • Web scanning
  • Dependency scanning
  • False-positive review
04

Security considerations

  • Scans scheduled to avoid disruption
  • Results validated before reporting
  • Secure delivery of reports
05

Typical integrations

  • Cloud accounts
  • Container registries
06

Recommended technology

  • Nmap
  • Trivy
  • OWASP ZAP
07

Expected outcome

Known vulnerabilities found and tracked to closure.

08

Timeline

Website security audit
1–2 weeks
API or application assessment
2–4 weeks
Secure code review
1–4 weeks, by codebase size
Hardening engagement
1–3 weeks

Typical ranges for cyber security projects. Confirmed after discovery; not a guarantee.

09

Engagement model

  1. 01Fixed scopeA defined scope, price and timeline. Best when requirements are clear.
  2. 02Dedicated teamA monthly team for ongoing product development and priorities that change.
  3. 03Time and materialsBilled by effort for discovery, assessments or evolving work, with regular reporting.

Our delivery standard

The same ten stages apply to every cyber security engagement, scaled to the size of the project.

Full process →
  1. 01Requirement discovery
  2. 02Scope definition
  3. 03Architecture
  4. 04UX/UI
  5. 05Development
  6. 06Security review
  7. 07Testing
  8. 08Client review
  9. 09Deployment
  10. 10Post-launch support

Discuss your vulnerability assessment project

Tell us what you're building. We reply with questions, a suggested approach and next steps.