
This cheat sheet presents recommendations for creating a strong report as part of an information security assessment project. To print, use the one-sheet PDF version; you can also edit the Word version for you own needs.
Your analysis should provide value beyond regurgitating the data already in existence.
Consider what information provided to you is incomplete or might be a lie or half-truth.
Group initial findings based on affected resources, risk, issue category, etc. to look for patterns.
Identify for trends that highlight the existence of underlying problems that affect security.
If examining scanner output, consider exploring the data using spreadsheets and pivot tables.
Fill in the gaps in your understanding with follow-up scans, document requests and/or interviews.
Involve colleagues in your analysis to obtain other people’s perspectives on the data and conclusions.
Document the methodology used to perform the assessment, analyze data and prioritize findings.
The methodology's description need to demonstrate a systemic and well-reasoned assessment approach.
Clarify the type of the assessment performed: penetration test, vulnerability assessment, etc.
If applicable, explain what security assessment tools were used and how they were configured.
If applicable, describe what approach guided the questions you asked during interviews.
Describe the criteria used to assign severity or criticality levels to the findings of the assessment.
Refer to the relevant frameworks you used to guide the assessment efforts (PCI DSS, ISO 27001, etc.).
Specify what systems, networks and/or applications were reviewed as part of the security assessment.
State what documentation was reviewed if any.
List the people whom you interviewed, if any.
Clarify the primary goals of the assessment project.
Discuss what contractual obligations or regulatory requirements were accounted for in the assessment.
Document any items that were specifically excluded from the assessment's scope and explain why.
Include both negative and positive findings.
Account for organization's industry, business model and compliance requirements where appropriate.
Stay consistent with the methodology and scope.
Prioritize findings related to security risks.
Provide practical remediation path, accounting for the organization’s strengths and weaknesses.
Create templates based on prior reports, so you don't have to write every document from scratch.
Safeguard (encrypt) the report when storing and sending it, since its contents are probably sensitive.
Use concrete statements; avoid passive voice.
Explain the significance of the security findings in the context of current threats and events.
Put effort into making the report as brief as possible without omitting important and relevant contents.
6 Qualities of a Good Information Security Report
4 Tips for a Strong Executive Summary of a Security Assessment Report
Security Assessment Report as Critique, Not Criticism
4 Reasons Why Security Assessment Recommendations Get Ignored
Dealing with Misinformation During Security Assessments
Special thanks for feedback to Dave Shackleford and John Strand. If you have suggestions for improving this cheat sheet, please let me know.
This cheat sheet is distributed according to the Creative Commons v3 "Attribution" License. File version 1.0.
Take a look at my other security cheat sheets.
About the Author: Lenny Zeltser is a seasoned IT professional with a strong background in information security and business management. His areas of expertise include cloud services and malicious software. Lenny focuses on safeguarding customers' IT operations at Radiant Systems. He also teaches how to analyze and combat malware at SANS Institute. Lenny explores security topics at conferences, in books and in articles. He also volunteers as an incident handler at the Internet Storm Center. You should follow Lenny on Twitter and read his blog.
Copyright © 1995-2012 Lenny Zeltser. All rights reserved. RSS Feed.
The information on this site does not necessarily represent positions or opinions of my employer.