An intrusion prevention system (IPS) detects and blocks potential threats targeting an organization’s systems and applications. Cloud IPS is an integral component of an organization’s cloud and edge security strategy. A cloud IPS key helps support a workforce that is primarily remote, for example, as part of a move to Secure Access Service Edge (SASE) and cloud-based network security. Cloud IPS is also integral to cloud-migration initiatives that require native cloud security to protect an organization’s IaaS.
An intrusion prevention system (IPS) is similar to an intrusion detection system (IDS) but goes a step further. Like an IDS, an IPS can use signature or anomaly-based detection to identify potentially malicious communications or access attempts in network traffic. An IPS can be deployed to protect a particular host, or at the enterprise perimeter to protect an entire network.
The combination of signature and anomaly-based detection enables an IPS to detect and respond to both known threats, such as those assigned Common Vulnerabilities and Exposures (CVEs) and common errors as described in the OWASP Top Ten, and zero-day threats. An IPS prevents the exploitation of applications such as Adobe Acrobat and browser exploits, and prevents attacks such as Log4J and other well-known vulnerabilities documented in the CVE database.
The main difference between an IDS and an IPS, is that an IDS is focused on detecting and generating alerts about potential threats, while an IPS also blocks malicious connections or access attempts. An IDS may be deployed as an inline sensor that monitors the traffic it is protecting, or as a passive sensor that monitors a copy of the traffic through a network tap. However, to enable blocking malicious communications in real time, an IPS needs to be deployed inline.
A cloud IPS is an IPS deployed in the cloud to protect sensitive resources when they are accessed remotely, or alternatively, to protect cloud-based resources as part of IaaS security..
A cloud IPS can be deployed as a standalone solution or as part of an integrated security product. For example, an IPS may be integrated into a next-generation branch firewall-as-a-service (Next Generation FWaaS), a cloud-native FWaaS for IaaS environments or be deployed as part of a Secure Access Service Edge (SASE) offering. Alternatively, an organization may be able to take advantage of the functionality of an IPS via a service model.
Cloud and on-prem IPS have the same purpose of identifying and blocking attempted attacks against an organization’s resources. They differ largely in how they are deployed and the resources that they protect.
An on-prem IPS can be deployed as a standalone physical appliance, virtualized solution, or integrated into another product such as an NGFW. It protects the users and applications connected to the enterprise internal network.
A cloud IPS, on the other hand, is deployed in a service-based model from the cloud, either as a standalone solution, or as part of integrated security solutions for remote user access, branch access or cloud data centers and production environments (IaaS). Depending on the deployment model, it may therefore be used to protect only IaaS, or a combination of IaaS and on-premises services for remote users and branches.
A cloud IPS must offer certain features to prevent attacks against the protected network, including:
Cloud IPS can provide significant benefits to an organization, such as:
SASE solution that integrates cloud IPS into a full security stack delivered from the cloud to secure remote access to on-prem and IaaS resources, as well as protect branch office connections. To learn more about SASE and how it can help secure your organization’s remote and hybrid workers,
Check Point’s SASE offering — delivers ZTNA, SWG, CASB, and FWaaS to protect users and branch offices with zero-trust access control, advanced threat prevention, and data protection. Explore the capabilities of Harmony SASE for yourself with a free demo today.