← Back to Portfolio

Security Checklists & Templates

CMMC L2, CIS Controls, IR Playbooks | Downloadable Assessment Tools

Download CMMC Level 2 Assessment Checklist:

0% Complete (0/110)
CMMC Level 2 Compliance Assessment
Cybersecurity Maturity Model Certification (CMMC) 2.0 Level 2 requires implementation of all 110 practices across 14 security domains. This comprehensive checklist maps to NIST SP 800-171 requirements for protecting Controlled Unclassified Information (CUI). Use this to assess your organization's compliance posture and identify gaps.
AC - Access Control (22 Practices) ▼
AC.L2-3.1.1 Limit system access to authorized users, processes acting on behalf of authorized users, and devices (including other systems).
AC.L2-3.1.2 Limit system access to the types of transactions and functions that authorized users are permitted to execute.
AC.L2-3.1.3 Control the flow of CUI in accordance with approved authorizations.
AC.L2-3.1.4 Separate the duties of individuals to reduce the risk of malevolent activity without collusion.
AC.L2-3.1.5 Employ the principle of least privilege, including for specific security functions and privileged accounts.
AC.L2-3.1.6 Use non-privileged accounts or roles when accessing nonsecurity functions.
AC.L2-3.1.7 Prevent non-privileged users from executing privileged functions and capture the execution of such functions in audit logs.
AC.L2-3.1.8 Limit unsuccessful logon attempts.
AC.L2-3.1.9 Provide privacy and security notices consistent with applicable CUI rules.
AC.L2-3.1.10 Use session lock with pattern-hiding displays to prevent access and viewing of data after period of inactivity.
AC.L2-3.1.11 Terminate (automatically) a user session after a defined condition.
AC.L2-3.1.12 Monitor and control remote access sessions.
AC.L2-3.1.13 Employ cryptographic mechanisms to protect the confidentiality of remote access sessions.
AC.L2-3.1.14 Route remote access via managed access control points.
AC.L2-3.1.15 Authorize remote execution of privileged commands and remote access to security-relevant information.
AC.L2-3.1.16 Authorize wireless access prior to allowing such connections.
AC.L2-3.1.17 Protect wireless access using authentication and encryption.
AC.L2-3.1.18 Control connection of mobile devices.
AC.L2-3.1.19 Encrypt CUI on mobile devices and mobile computing platforms.
AC.L2-3.1.20 Verify and control/limit connections to and use of external systems.
AC.L2-3.1.21 Limit use of portable storage devices on external systems.
AC.L2-3.1.22 Control CUI posted or processed on publicly accessible systems.
AT - Awareness and Training (5 Practices) ▼
AT.L2-3.2.1 Ensure that managers, systems administrators, and users of organizational systems are made aware of the security risks associated with their activities and of the applicable policies, standards, and procedures related to the security of those systems.
AT.L2-3.2.2 Ensure that personnel are trained to carry out their assigned information security-related duties and responsibilities.
AT.L2-3.2.3 Provide security awareness training on recognizing and reporting potential indicators of insider threat.
AT.L2-3.2.4 Provide awareness training focused on recognizing and responding to threats from social engineering, advanced persistent threat actors, breaches, and suspicious behaviors.
AT.L2-3.2.5 Update security awareness training content based on the frequency of new threat vectors and attack techniques.
AU - Audit and Accountability (9 Practices) ▼
AU.L2-3.3.1 Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity.
AU.L2-3.3.2 Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions.
AU.L2-3.3.3 Review and update logged events.
AU.L2-3.3.4 Alert in the event of an audit logging process failure.
AU.L2-3.3.5 Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity.
AU.L2-3.3.6 Provide audit record reduction and report generation to support on-demand analysis and reporting.
AU.L2-3.3.7 Provide a system capability that compares and synchronizes internal system clocks with an authoritative source to generate time stamps for audit records.
AU.L2-3.3.8 Protect audit information and audit logging tools from unauthorized access, modification, and deletion.
AU.L2-3.3.9 Limit management of audit logging functionality to a subset of privileged users.
CM - Configuration Management (9 Practices) ▼
CM.L2-3.4.1 Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles.
CM.L2-3.4.2 Establish and enforce security configuration settings for information technology products employed in organizational systems.
CM.L2-3.4.3 Track, review, approve or disapprove, and log changes to organizational systems.
CM.L2-3.4.4 Analyze the security impact of changes prior to implementation.
CM.L2-3.4.5 Define, document, approve, and enforce physical and logical access restrictions associated with changes to organizational systems.
CM.L2-3.4.6 Employ the principle of least functionality by configuring organizational systems to provide only essential capabilities.
CM.L2-3.4.7 Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services.
CM.L2-3.4.8 Apply deny-by-exception (blacklisting) policy to prevent the use of unauthorized software or deny-all, permit-by-exception (whitelisting) policy to allow the execution of authorized software.
CM.L2-3.4.9 Control and monitor user-installed software.
IA - Identification and Authentication (11 Practices) ▼
IA.L2-3.5.1 Identify system users, processes acting on behalf of users, and devices.
IA.L2-3.5.2 Authenticate (or verify) the identities of users, processes, or devices, as a prerequisite to allowing access to organizational systems.
IA.L2-3.5.3 Use multifactor authentication for local and network access to privileged accounts and for network access to non-privileged accounts.
IA.L2-3.5.4 Employ replay-resistant authentication mechanisms for network access to privileged and non-privileged accounts.
IA.L2-3.5.5 Prevent reuse of identifiers for a defined period.
IA.L2-3.5.6 Disable identifiers after a defined period of inactivity.
IA.L2-3.5.7 Enforce a minimum password complexity and change of characters when new passwords are created.
IA.L2-3.5.8 Prohibit password reuse for a specified number of generations.
IA.L2-3.5.9 Allow temporary password use for system logons with an immediate change to a permanent password.
IA.L2-3.5.10 Store and transmit only cryptographically-protected passwords.
IA.L2-3.5.11 Obscure feedback of authentication information.
IR - Incident Response (8 Practices) ▼
IR.L2-3.6.1 Establish an operational incident-handling capability for organizational systems that includes preparation, detection, analysis, containment, recovery, and user response activities.
IR.L2-3.6.2 Track, document, and report incidents to designated officials and/or authorities both internal and external to the organization.
IR.L2-3.6.3 Test the organizational incident response capability.
IR.L2-3.6.4 Develop and implement responses to declared incidents according to pre-defined procedures.
IR.L2-3.6.5 Perform root cause analysis on incidents to determine underlying causes.
IR.L2-3.6.6 Monitor and report the effectiveness of incident response activities.
IR.L2-3.6.7 Establish and maintain contact with security groups and associations to receive security alerts and advisories.
IR.L2-3.6.8 Employ automated mechanisms to assist in the tracking of security incidents and in the collection and analysis of incident information.
MA - Maintenance (6 Practices) ▼
MA.L2-3.7.1 Perform maintenance on organizational systems.
MA.L2-3.7.2 Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance.
MA.L2-3.7.3 Ensure equipment removed for off-site maintenance is sanitized of any CUI.
MA.L2-3.7.4 Check media containing diagnostic and test programs for malicious code before the media are used in organizational systems.
MA.L2-3.7.5 Require multifactor authentication to establish nonlocal maintenance sessions via external network connections and terminate such connections when nonlocal maintenance is complete.
MA.L2-3.7.6 Supervise the maintenance activities of maintenance personnel without required access authorization.
MP - Media Protection (8 Practices) ▼
MP.L2-3.8.1 Protect (i.e., physically control and securely store) system media containing CUI, both paper and digital.
MP.L2-3.8.2 Limit access to CUI on system media to authorized users.
MP.L2-3.8.3 Sanitize or destroy system media containing CUI before disposal or release for reuse.
MP.L2-3.8.4 Mark media with necessary CUI markings and distribution limitations.
MP.L2-3.8.5 Control access to media containing CUI and maintain accountability for media during transport outside of controlled areas.
MP.L2-3.8.6 Implement cryptographic mechanisms to protect the confidentiality of CUI stored on digital media during transport unless otherwise protected by alternative physical safeguards.
MP.L2-3.8.7 Control the use of removable media on system components.
MP.L2-3.8.8 Prohibit the use of portable storage devices when such devices have no identifiable owner.
PE - Physical Protection (6 Practices) ▼
PE.L2-3.10.1 Limit physical access to organizational systems, equipment, and the respective operating environments to authorized individuals.
PE.L2-3.10.2 Protect and monitor the physical facility and support infrastructure for organizational systems.
PE.L2-3.10.3 Escort visitors and monitor visitor activity.
PE.L2-3.10.4 Maintain audit logs of physical access.
PE.L2-3.10.5 Control and manage physical access devices.
PE.L2-3.10.6 Enforce safeguarding measures for CUI at alternate work sites.
PS - Personnel Security (2 Practices) ▼
PS.L2-3.9.1 Screen individuals prior to authorizing access to organizational systems containing CUI.
PS.L2-3.9.2 Ensure that organizational systems containing CUI are protected during and after personnel actions such as terminations and transfers.
RE - Recovery (5 Practices) ▼
RE.L2-3.11.1 Regularly perform and test data backups.
RE.L2-3.11.2 Protect the confidentiality of backup CUI at storage locations.
RE.L2-3.11.3 Separately store backup copies of CUI.
RE.L2-3.11.4 Implement recovery procedures to restore system operations, CUI, and system capabilities after a disruption or failure.
RE.L2-3.11.5 Regularly test backup and restoration processes to ensure system recovery.
RM - Risk Assessment (4 Practices) ▼
RM.L2-3.11.1 Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the associated processing, storage, or transmission of CUI.
RM.L2-3.11.2 Scan for vulnerabilities in organizational systems and applications periodically and when new vulnerabilities affecting those systems and applications are identified.
RM.L2-3.11.3 Remediate vulnerabilities in accordance with risk assessments.
RM.L2-3.11.4 Update threat profiles and attack vectors based on emerging threats and vulnerabilities.
CA - Security Assessment (9 Practices) ▼
CA.L2-3.12.1 Periodically assess the security controls in organizational systems to determine if the controls are effective in their application.
CA.L2-3.12.2 Develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems.
CA.L2-3.12.3 Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
CA.L2-3.12.4 Develop, document, and periodically update system security plans that describe system boundaries, system environments of operation, how security requirements are implemented, and the relationships with or connections to other systems.
CA.L2-3.12.5 Establish and maintain a cyber threat hunting capability to search for indicators of compromise in organizational systems and detect, track, and disrupt threats that evade existing controls.
CA.L2-3.12.6 Employ automated mechanisms to detect misconfigured or unauthorized systems and software.
CA.L2-3.12.7 Employ automated mechanisms to identify and respond to security-related anomalies.
CA.L2-3.12.8 Analyze communications traffic patterns and event/incident data to identify anomalies and indicators of potential threats.
CA.L2-3.12.9 Employ security assessment results and analysis to inform the Plan of Action and Milestones (POA&M) process.
SC - System and Communications Protection (20 Practices) ▼
SC.L2-3.13.1 Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems.
SC.L2-3.13.2 Employ architectural designs, software development techniques, and systems engineering principles that promote effective information security within organizational systems.
SC.L2-3.13.3 Separate user functionality from system management functionality.
SC.L2-3.13.4 Prevent unauthorized and unintended information transfer via shared system resources.
SC.L2-3.13.5 Implement subnetworks for publicly accessible system components that are physically or logically separated from internal networks.
SC.L2-3.13.6 Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception).
SC.L2-3.13.7 Prevent remote devices from simultaneously establishing non-remote connections with organizational systems and communicating via some other connection to resources in external networks (i.e., split tunneling).
SC.L2-3.13.8 Implement cryptographic mechanisms to prevent unauthorized disclosure of CUI during transmission unless otherwise protected by alternative physical safeguards.
SC.L2-3.13.9 Terminate network connections associated with communications sessions at the end of the sessions or after a defined period of inactivity.
SC.L2-3.13.10 Establish and manage cryptographic keys for cryptography employed in organizational systems.
SC.L2-3.13.11 Employ FIPS-validated cryptography when used to protect the confidentiality of CUI.
SC.L2-3.13.12 Prohibit remote activation of collaborative computing devices and provide indication of devices in use to users present at the device.
SC.L2-3.13.13 Control and monitor the use of mobile code.
SC.L2-3.13.14 Control and monitor the use of Voice over Internet Protocol (VoIP) technologies.
SC.L2-3.13.15 Protect the authenticity of communications sessions.
SC.L2-3.13.16 Protect the confidentiality of CUI at rest.
SC.L2-3.13.17 Employ cryptography to protect CUI at rest and in transit.
SC.L2-3.13.18 Identify, report, and correct information and system flaws in a timely manner.
SC.L2-3.13.19 Provide protection from malicious code at designated locations within organizational systems.
SC.L2-3.13.20 Monitor system security alerts and advisories and take action in response.
SI - System and Information Integrity (11 Practices) ▼
SI.L2-3.14.1 Identify, report, and correct system flaws in a timely manner.
SI.L2-3.14.2 Provide protection from malicious code at designated locations within organizational systems.
SI.L2-3.14.3 Monitor system security alerts and advisories and take action in response.
SI.L2-3.14.4 Update malicious code protection mechanisms when new releases are available.
SI.L2-3.14.5 Perform periodic scans of organizational systems and real-time scans of files from external sources as files are downloaded, opened, or executed.
SI.L2-3.14.6 Monitor organizational systems, including inbound and outbound communications traffic, to detect attacks and indicators of potential attacks.
SI.L2-3.14.7 Identify unauthorized use of organizational systems.
SI.L2-3.14.8 Employ spam protection mechanisms at information system entry and exit points.
SI.L2-3.14.9 Deploy monitoring devices strategically within the system to collect organization-determined essential information; and at ad hoc locations within the system to track specific types of transactions of interest to the organization.
SI.L2-3.14.10 Analyze the security impact of changes prior to implementation.
SI.L2-3.14.11 Correlate information from monitoring tools and detection systems.

Download CIS Controls v8 Implementation Guide:

0% Complete (0/18)
CIS Controls Version 8 Implementation Checklist
The Center for Internet Security (CIS) Controls are a prioritized set of actions to protect your organization from known cyber attack vectors. This checklist covers all 18 controls across Implementation Groups 1, 2, and 3.
Basic CIS Controls (Implementation Group 1) ▼
CIS 1 Inventory and Control of Enterprise Assets - Actively manage (inventory, track, and correct) all enterprise assets connected to the infrastructure
CIS 2 Inventory and Control of Software Assets - Actively manage (inventory, track, and correct) all software on the network
CIS 3 Data Protection - Develop processes and technical controls to identify, classify, securely handle, retain, and dispose of data
CIS 4 Secure Configuration of Enterprise Assets and Software - Establish and maintain secure configurations for all technology assets
CIS 5 Account Management - Use processes and tools to assign and manage authorization to credentials for user, admin, and service accounts
CIS 6 Access Control Management - Use processes and tools to create, assign, manage, and revoke access credentials and privileges
CIS 7 Continuous Vulnerability Management - Develop a plan to continuously assess and track vulnerabilities on all assets
CIS 8 Audit Log Management - Collect, alert, review, and retain audit logs of events that could help detect, understand, or recover from an attack
CIS 9 Email and Web Browser Protections - Improve defenses and reduce attack surface for email and web browsers
CIS 10 Malware Defenses - Control the installation, spread, and execution of malicious applications, code, or scripts
CIS 11 Data Recovery - Establish and maintain data recovery practices sufficient to restore in-scope assets
CIS 12 Network Infrastructure Management - Establish, implement, and actively manage (track, report, correct) network devices
CIS 13 Network Monitoring and Defense - Operate processes and tooling to establish and maintain comprehensive network monitoring
CIS 14 Security Awareness and Skills Training - Establish and maintain a security awareness program to influence behavior
CIS 15 Service Provider Management - Develop a process to evaluate service providers for security posture
CIS 16 Application Software Security - Manage the security lifecycle of in-house developed, hosted, or acquired software
CIS 17 Incident Response Management - Establish a program to develop and maintain an incident response capability
CIS 18 Penetration Testing - Test the effectiveness and resiliency of assets through identifying and exploiting weaknesses

Download Incident Response Playbooks:

Incident Response Playbook Library
Comprehensive incident response playbooks for common security incidents. Each playbook provides step-by-step guidance for detection, containment, eradication, and recovery.
Ransomware Incident Response Playbook ▼

Phase 1: Detection & Analysis

Identify scope of encryption - number of systems affected, data types, critical systems
Capture ransom note and file extensions for variant identification
Review logs to identify initial access vector (email, RDP, vulnerability)
Check for lateral movement indicators and privilege escalation

Phase 2: Containment

Isolate affected systems from network (DO NOT power off - may destroy forensic evidence)
Disable user accounts suspected of compromise
Block C2 domains and IPs at firewall
Reset credentials for all administrative accounts
Secure and protect backups (take offline if possible)

Phase 3: Eradication

Identify and remove malware/ransomware binaries
Remove persistence mechanisms (scheduled tasks, registry keys, services)
Patch vulnerabilities exploited for initial access
Rebuild compromised systems from known-good baseline

Phase 4: Recovery

Restore data from clean backups (verify backup integrity first)
Verify restored systems are malware-free before reconnecting to network
Monitor restored systems for 48-72 hours for re-infection
Return systems to production in phased approach

Phase 5: Post-Incident

Conduct lessons learned meeting within 7 days
Document timeline, actions taken, and root cause
Implement security improvements to prevent recurrence
Update incident response plan based on lessons learned
Phishing/Business Email Compromise Playbook ▼

Phase 1: Detection & Analysis

Obtain copy of phishing email with full headers
Analyze sender address, reply-to, and email path (SPF, DKIM, DMARC)
Identify payload type (credential harvesting, malware, wire fraud)
Search email logs for similar messages to determine scope
Identify users who clicked links or opened attachments

Phase 2: Containment

Create email filter rule to block sender domain/address
Purge malicious emails from all mailboxes
Block malicious URLs at web proxy/firewall
Reset passwords for users who entered credentials
Enable MFA if not already enforced

Phase 3: Eradication

Review email forwarding rules and mailbox permissions
Remove unauthorized mailbox delegates or application consents
Scan systems of affected users for malware
Review Azure AD/Entra sign-in logs for suspicious authentications

Phase 4: Recovery

Restore any deleted/moved emails if BEC occurred
Contact financial institutions if wire fraud attempted
Monitor compromised accounts for 30 days

Phase 5: Post-Incident

Conduct phishing awareness training for affected users
Review and enhance email security controls (DMARC, ATP, etc.)
Implement simulated phishing campaigns
Data Breach/Exfiltration Playbook ▼

Phase 1: Detection & Analysis

Identify data exfiltration indicators (large uploads, cloud storage access, unusual destinations)
Determine what data was accessed/exfiltrated
Identify affected individuals and data types (PII, PHI, financial)
Determine method of exfiltration (email, cloud, removable media, FTP)
Assess if breach notification requirements apply (GDPR, HIPAA, state laws)

Phase 2: Containment

Disable compromised accounts immediately
Block exfiltration destinations (IPs, domains, cloud storage)
Implement DLP rules to prevent further exfiltration
Isolate affected systems
Notify legal counsel and executive leadership

Phase 3: Eradication

Remove attacker access and persistence mechanisms
Patch vulnerabilities that enabled breach
Review and revoke excessive data access permissions

Phase 4: Recovery & Notification

Notify affected individuals per regulatory requirements (72 hours for GDPR)
Notify regulatory bodies as required (HHS, state AGs, etc.)
Offer credit monitoring if PII/financial data compromised
Prepare public statement if necessary

Phase 5: Post-Incident

Document full incident timeline for regulatory compliance
Implement data classification and DLP solutions
Review and update data access controls and least privilege
Insider Threat Playbook ▼

Phase 1: Detection & Analysis

Review behavioral indicators (unusual hours, mass downloads, resignations, performance issues)
Analyze data access logs for unusual patterns
Check for use of personal cloud storage, email forwarding, USB devices
Coordinate with HR for employment status and disciplinary history
Determine intent (malicious vs negligent) and motive

Phase 2: Containment

Disable user account access (coordinate timing with HR if termination)
Collect and preserve evidence before account disabled (disk images, logs)
Revoke physical access badges and VPN access
Monitor for any access attempts post-termination
Notify legal counsel - may involve law enforcement or civil litigation

Phase 3: Investigation

Conduct forensic analysis of user's devices
Review email, chat logs, and file sharing activity
Identify what data was accessed and if it was shared externally
Document chain of custody for all evidence

Phase 4: Recovery

Reset credentials for systems insider had access to
Review and revoke excessive permissions across organization
Notify affected parties if sensitive data compromised

Phase 5: Post-Incident

Implement User and Entity Behavior Analytics (UEBA)
Enhance DLP and data access monitoring
Review and improve offboarding procedures
Conduct insider threat awareness training

Download security assessment and incident report templates:

Security Report Templates
Professional templates for documenting security assessments, incidents, and compliance activities. All templates follow industry best practices and compliance frameworks.
Available Report Templates

Vulnerability Assessment Report Template

Comprehensive template for documenting vulnerability scans and assessments

  • Executive Summary
  • Scope and Methodology
  • Findings by Severity (Critical, High, Medium, Low)
  • Remediation Recommendations with Timelines
  • Risk Matrix and CVSS Scoring
  • Compliance Gap Analysis

Incident Response Report Template

Detailed template for documenting security incidents from detection to resolution

  • Incident Summary and Classification
  • Timeline of Events
  • Impact Assessment (systems, data, users)
  • Root Cause Analysis
  • Containment and Eradication Actions
  • Lessons Learned and Recommendations
  • Regulatory Notification Requirements

Penetration Test Report Template

Professional pentest report format with MITRE ATT&CK mapping

  • Executive Summary (Non-Technical)
  • Test Scope, Rules of Engagement, Limitations
  • Attack Narrative and Kill Chain Analysis
  • Detailed Findings with Proof of Concept
  • MITRE ATT&CK Technique Mapping
  • Remediation Guidance and Retest Results
  • Appendices (Tools, Commands, Screenshots)

Risk Assessment Template

Structured risk assessment following NIST RMF and ISO 27005

  • Asset Inventory and Valuation
  • Threat and Vulnerability Identification
  • Likelihood and Impact Analysis
  • Risk Scoring Matrix (Qualitative/Quantitative)
  • Risk Treatment Options (Accept, Mitigate, Transfer, Avoid)
  • Control Recommendations and Cost-Benefit Analysis
  • Residual Risk Assessment