How to Install and Uninstall owasp-modsecurity-crs Package on openSUSE Leap

Last updated: December 23,2024

1. Install "owasp-modsecurity-crs" package

Here is a brief guide to show you how to install owasp-modsecurity-crs on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                owasp-modsecurity-crs
            
                    
    
    Copied

2. Uninstall "owasp-modsecurity-crs" package

This guide covers the steps necessary to uninstall owasp-modsecurity-crs on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                owasp-modsecurity-crs
            
                    
    
    Copied

3. Information about the owasp-modsecurity-crs package on openSUSE Leap

Information for package owasp-modsecurity-crs:
----------------------------------------------
Repository : Main Repository
Name : owasp-modsecurity-crs
Version : 2.2.9-bp155.3.10
Arch : noarch
Vendor : openSUSE
Installed Size : 390.6 KiB
Installed : No
Status : not installed
Source package : owasp-modsecurity-crs-2.2.9-bp155.3.10.src
Upstream URL : https://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project
Summary : OWASP ModSecurity Common Rule Set (CRS)
Description :
ModSecurity™ is a web application firewall engine that provides very little protection on its own. In order to become useful, ModSecurity™ must be configured with rules. In order to enable users to take full advantage of ModSecurity™ out of the box, Trustwave's SpiderLabs is providing a free certified rule set for ModSecurity™ 2.x. Unlike intrusion detection and prevention systems, which rely on signatures specific to known vulnerabilities, the Core Rules provide generic protection from unknown vulnerabilities often found in web applications, which are in most cases custom coded. The Core Rules are heavily commented to allow it to be used as a step-by-step deployment guide for ModSecurity™.
Core Rules Content
In order to provide generic web applications protection, the Core Rules use the following techniques:
HTTP Protection - detecting violations of the HTTP protocol and a locally defined usage policy.
Real-time Blacklist Lookups - utilizes 3rd Party IP Reputation
Web-based Malware Detection - identifies malicious web content by check against the Google Safe Browsing API.
HTTP Denial of Service Protections - defense against HTTP Flooding and Slow HTTP DoS Attacks.
Common Web Attacks Protection - detecting common web application security attack.
Automation Detection - Detecting bots, crawlers, scanners and other surface malicious activity.
Integration with AV Scanning for File Uploads - detects malicious files uploaded through the web application.
Tracking Sensitive Data - Tracks Credit Card usage and blocks leakages.
Trojan Protection - Detecting access to Trojans horses.
Identification of Application Defects - alerts on application misconfigurations.
Error Detection and Hiding - Disguising error messages sent by the server.