Establish Proof of Security Testing
Once the SLA is established, it is important to make sure that both sides are clear about the nature, levels and frequency of independent security testing. As part of this, look to the CSP to provide specific documents that describe the security practices they utilize. These may include, for example, penetration of the CSP’s wired and wireless network, or its web applications. The frequency of testing should be determined based on your company’s specific needs, with quarterly or semi-annual checks as the most commonplace. Annual is not enough and leaves room for vulnerabilities to go unnoticed for too long. Likewise, monthly security testing is too frequent and would not show enough of a substantial change to identify risks or exposure points.
How to Assess Your Critical Cloud Service Providers
How to Assess Your Critical Cloud Service Providers
Previously, MetricStream's David Williamson shared best practices for how companies can keep their cloud technologies secure, including:
- Prioritizing the value of your data (whether public or private).
- Considering the different ways a loss event may impact your organization.
- Monitoring and managing your third-party relationships with specific loss prevention protocols.
- Testing your network for weaknesses, and addressing them swiftly.
- Dedicating resources for information stewardship.
According to the Global State of Information Survey led by PwC US in conjunction with CIO Magazine and CSO Magazine, of 10,000 IT and security decision-makers in 127 nations, 69 percent of respondents use cloud-based security services. This number reflects that the cloud has not only proliferated, but has become a staple in the enterprise IT strategy. Given the survey results, which reveal increasing and continued growth of cloud adoption, Williamson has outlined five best practice guidelines for how companies can assess the capabilities of their critical cloud service providers (CSP).
