Sample Documentation

Skills/Tools: Writing, Formatting, Tailoring for Audience, Identifying Purpose

As someone with a B.A. in English and Mathematics, who was a math teacher department chair at a high school for 6 years, and the same school's registrar, I am capable of writing technical, non-technical, and technical-in-a-non-technical-way documentation and tailoring it to the audience.

With documentation, it's about understanding the following things:

1. What is the preferred format?

2. Who is the audience? (not just their name, but their expertise, their role, their preferences, their priorities, etc.)

3. What is the purpose (or purposes) of what is being written?

If I know the answers to those questions, I can write what is needed.

Sample Documentation

1. Incident Handler's Journal

• Tools/Skills: Documentation, Playbooks, Wireshark, Splunk, Chronicle, VirusTotal, Incident Response Post-Incident Analysis, Logs, linux cli, tcpdump

2. Incident Reports

• Network Traffic Analysis (technical & non-technical descriptions)

• DDos Attack (technical & non-technical descriptions)

• Website Redirection (technical & non-technical descriptions)

3. Risk Assessment Report

4. Email regarding Zero-day Vulnerability