Lion Cipher Lab
Trend recurring findings across annual penetration tests
- Penetration Testing / Red Team
- Intermediate
- ~45 min
- Free · no account required
Why it matters
Many organizations commission a penetration test every year, fix the findings, and file the report. Read one at a time, each report looks like progress: most of last year's findings are gone. Read side by side, the same weaknesses often keep returning. They are fixed on the servers named in the report and reappear on new servers, or they come back after a rebuild, or a different bug of the same kind turns up in the same application. That pattern is the most valuable thing a series of tests can show, because it points at the process that keeps producing the findings: patching, configuration…
What you'll learn
- comparing findings across successive tests
- fingerprinting a finding so it matches across years
- new, recurring and fixed counts, and recurrence rate
- per-host versus class-level matching
- attributing recurrence to root causes
- turning trend data into program-level recommendations
- what a trend analysis cannot show
Steps in this lab
- What a series of tests can show that one test cannot
- Three years of findings
- Write the trend script
- Run it per host
- Run it by class, and find what neither view shows
- Turn the trend into recommendations