Lesson 6.3: Final mission: a security assessment from authorisation to report
The whole course in one job. You receive a written authorisation for two machines in a lab, check that you're inside the time window, discover the hosts, identify their services and versions, read the public web pages and find a database backup listed for anyone, stop at proof as the rules require, rate what you found, write the findings and fingerprint the report. Ethics, law, attack stages, defence and reporting, all in one sitting.
22 min
You will learn to
- Check an authorisation and its time window before acting
- Discover hosts and identify services and versions
- Find exposed information on a web server without exploiting it
- Rate findings by severity
- Write and fingerprint a findings report
Key terms
- Finding
- One security problem you identified, with where it is and the evidence.
- Severity
- How bad a finding is, usually from likelihood and impact (section 2): critical, high, medium, low, informational.
- Remediation
- The recommended fix for a finding.
- Executive summary
- The first page of a report, for non-technical readers: what was tested, how bad it is overall, what to do first.
← Package management on Debian and Ubuntu: apt · All lessons · Package management on Red Hat systems: dnf →