Colony Favorites

This zip file contains a number of information security policies based on both the NIST 800-53r5 and NIST CSF frameworks. In addition, there are templates for writing other policies as well. The package is not meant to be comprehensive and cover absolutely everything needed but it certainly lays a solid groundwork for any organization adapting these frameworks to their requirements.

The processes used in Trustwave's Managed Vendor Risk Assessment service have been gathered together in this zip file to allow Security Colony subscribers to use these resources for themselves. Additionally, subscribers who want to use these resources will be entitled to a free consulting session with our MVRA experts to discuss the process.

The Company is currently implementing a project to enable the classification of data using Microsoft Azure Information Protection (AIP) solution. As part of this project, Trustwave was engaged to conduct a security assessment of the proposed AIP solution. The purpose of the assessment was to examine the security posture of the AIP environment, document perceived threats and identify potential security weaknesses.

A company recognized the need to move to the NIST CSF which enables a more robust, governed, agile, risk-based program that meets Federal requirements, industry standards, and best practices. To assist the transition the company contracted with Trustwave to conduct a security maturity assessment using their existing reporting templates and based on previous work that had been done.

In order to understand the current program maturity Trustwave worked with an organization to assess the security program against the National Institute of Standards and Technology (NIST) Cyber Security Framework (CSF), looking at the people, processes and technology to assess the current efficacy of the cyber program, identify areas for improvement and create a prioritized remediation road map

This playbook has been designed for the use of an Incident Response Team and relevant stakeholders including Third Party vendors when responding to Ransomware security incidents. It is not a standalone document and must be used alongside an Incident Response Plan (“IRP”) and supporting documentation.