Skip to content
StrikeOps
StrikeOps Library

Penetration test findings, written up properly

The findings that show up in almost every penetration test, written the way they should read in a client report: what it is, why it matters, how it was verified, the usual severity and how to fix it. Free to read and reuse as a starting point for your own write-ups.

Browse all 102 findings Free · Reviewed by offensive security operators
Findings
102
Areas
8
CWE-mapped
97

Typical severity mix

  • Critical5
  • High38
  • Medium36
  • Low22
  • Info1

48 findings also map to a MITRE ATT&CK technique. Ratings are a starting point; context decides.

All findings

Search and filter the library

Severity
Showing 102 of 102 findings

Network and infrastructure

Findings from external and internal network penetration tests: exposed services, weak protocols and unsupported software.

16 findings

Active Directory

Findings from internal and assumed-breach tests that give attackers a path from a standard user to domain admin.

15 findings

Web applications and APIs

Findings from web application and API penetration tests, from missing headers to access control flaws.

27 findings

Cloud and Microsoft 365

Findings from cloud configuration and identity reviews across Microsoft 365, Entra ID and AWS.

26 findings

Containers, CI/CD and source code

Findings from reviews of Kubernetes, containers, build pipelines and code repositories, where one leaked secret can expose production.

6 findings

Mobile applications

Findings from iOS and Android application penetration tests, covering the app, its storage and the APIs behind it.

4 findings

Email security

Findings that make spoofing, phishing and business email compromise easier.

6 findings

Wireless

Findings from wireless penetration tests of corporate and guest networks.

2 findings

How every write-up is structured

  1. DescriptionCopy-ready wording for what was found, as it should appear in the report.
  2. ImpactWhat an attacker can actually do with it, in business terms.
  3. SeverityThe usual rating, and what moves it up or down in context.
  4. How to verifyNon-destructive steps a professional tester can follow and evidence.
  5. RemediationOrdered, practical fixes the client's team can act on.
  6. Copy as MarkdownOne click to paste the write-up into your own report template.

About severity ratings

Each entry gives the severity a finding usually receives and what moves it up or down. Real ratings depend on context: exposure, the data and privileges involved, compensating controls and how findings chain together. Use these as a starting point and adjust them to the environment you tested.

Verification steps are written for professional testers working within an agreed scope and rules of engagement.

Get started

Stop rewriting the same findings

In StrikeOps, AI drafts each finding from your evidence on your own AI key, in your firm's voice and template. Your operators review and approve every word.

Open for business, licensing to offensive security firms now.

Book a demo