By 2020, 85 percent of large enterprises will use a cloud access security broker.*
According to Gartner, a cloud access security broker (CASB) is an on-premises or cloud-based security policy enforcement point that is placed between cloud service consumers and cloud service providers to combine and interject enterprise security policies as cloud-based resources are accessed. Organizations are increasingly turning to CASB to address cloud service risks, enforce security policies, and comply with regulations, even when cloud services are beyond their perimeter and out of their direct control. If you intend to use CASB to increase your confidence about your organization’s cloud service usage, consider taking a granular approach to policy enforcement and data protection. In other words, consider using a scalpel rather than a sledgehammer for your cloud security.
* Gartner. “Market Guide for Cloud Access Security Brokers.” October 24, 2016. Craig Lawson, Neil MacDonald, Brian Lowans, Brian Reed.
Companies need visibility and control across both sanctioned and unsanctioned services. Rather than take an “allow” or “block” stance on cloud services, cloud brokerage should enable IT to say “yes” to useful services while governing access to and activities and data within services. This could mean offering full access to a sanctioned suite like Microsoft Office 365 to users on corporate devices, but web-only email to users on unmanaged devices. It could also mean enforcing a “no sharing outside of the company” policy across a category of unsanctioned services. While cloud security is the key focus of a cloud access security broker, the other value is helping you get your arms around cloud spend. A CASB can help you discover all cloud services, report on what your cloud spend is, and find redundancies in functionality and license costs.
As organizations move more of their data and systems to the cloud, they must ensure they comply with the many regulations designed to ensure the safety and privacy of personal or corporate data. Cloud access security brokers can help ensure compliance in the cloud whether you are a healthcare organization worried about HIPAA or HITECH compliance, a retail company concerned with PCI compliance, or a financial services organization needing to comply with FFIEC and FINRA.
Accuracy comes from using highly sophisticated cloud DLP detection mechanisms like document fingerprinting, combined with reducing detection surface area using context (user, location, activity, etc.). When sensitive content is discovered in or en route to the cloud, the cloud access security broker (CASB) should allow IT the option of shuttling suspected violations efficiently to their on-premises systems for further analysis.
Organizations need to ensure their employees aren’t introducing or propagating cloud malware and threats through vectors such as cloud storage services and their associated sync clients and services. This means being able to scan and remediate threats in real time when an employee tries to share or upload an infected file or detecting and preventing unauthorized user access to cloud services and data. Protect yourself against a host of cloud threats including malware and insider threats with cloud malware and threat capabilities that combine threat intelligence, static and dynamic malware analysis, prioritized analysis, and remediation of threats that may originate from . or be further propagated by cloud services.”
Organizations need to ensure their employees aren’t introducing or propagating cloud malware and threats through vectors such as cloud storage services and their associated sync clients and services. This means being able to scan and remediate threats in real time when an employee tries to share or upload an infected file or detecting and preventing unauthorized user access to cloud services and data.
Protect yourself against a host of cloud threats including malware and insider threats with cloud malware and threat capabilities that combine threat intelligence, static and dynamic malware analysis, prioritized analysis, and remediation of threats that may originate from—or be further propagated by—cloud services.
Govern your organization’s cloud usage with granular visibility and control. Rather than take a coarse-grained approach by blocking services, govern usage based on identity, service, activity, and data. Define policies based on service category or risk and choose from actions such as block, alert, bypass, encrypt, quarantine, and coach for policy enforcement.
Protect and prevent the loss of sensitive data across all of the cloud services in your environment, not just the ones you sanction. Take advantage of advanced, enterprise DLP to discover and protect sensitive data in sanctioned cloud services and en route to or from any cloud service, sanctioned or unsanctioned, whether users are on premises, remote, on a mobile device, or accessing from a web browser, mobile app, or sync client.
Guard against cloud-based threats such as malware and ransomware. Start with full visibility of all cloud services, even those using SSL-encrypted connections, and use anomaly detection, and threat intelligence sources such as which of your users has compromised accounts. Then layer in static and dynamic anti-malware detections, plus machine learning to detect ransomware. Finally, arm the rest of your security infrastructure with your findings through out-of-the-box integrations and workflows.
Your organization is evaluating cloud access security brokers to safely enable sanctioned and unsanctioned cloud services. This 10-question checklist gives you specific, use case-based examples that will help you differentiate between the CASBs you may be evaluating.
Rather than take a sledgehammer to the service by blocking it, take a scalpel to an activity such as "share"; Do it at a category level – across any cloud storage service, for example. This lets you allow, not block services while mitigating risk.
Rather than find and secure content in just your sanctioned service, do it across both sanctioned and unsanctioned services, and for content that's at rest and en route. Also, minimize false positives and increase accuracy by reducing the surface area through context. Filter out the cloud transactions you care about by removing users, services, categories, locations, and activities from what you inspect and enforce policy.
Rather than upload or enter user data manually, enforce policies that incorporate groups from your enterprise directory such as Microsoft Active Directory.
Rather than detecting anomalies only in sanctioned services or at a coarse-grained level such as access, detect anomalies based on activities across any service, sanctioned or unsanctioned.
Rather than keep regulated services on-premises, migrate them to the cloud while also complying with regulations such as Sarbanes-Oxley. Report on access and data modifications within cloud-based systems of record.
Rather than exclude on-premises monitoring and control from your cloud security model, enforce your policies wherever your users are and whatever their device.
Identify and protect against users accessing your services with compromised account credentials.
Identify and protect against threats and malware in or en route to or from any cloud service.
Rather than deploy cloud security in a silo, make your existing investments more valuable by adding CASB.
Rather than be forced into a CASB vendor's deployment model, choose the deployment that best fits your requirements, now and in the future.