coraza | OWASP Coraza WAF is a golang modsecurity compatible web application firewall library | Firewall library

 by   corazawaf Go Version: v3.0.0 License: Apache-2.0

kandi X-RAY | coraza Summary

kandi X-RAY | coraza Summary

coraza is a Go library typically used in Security, Firewall applications. coraza has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library

            kandi-support Support

              coraza has a medium active ecosystem.
              It has 1112 star(s) with 140 fork(s). There are 25 watchers for this library.
              There were 4 major release(s) in the last 12 months.
              There are 20 open issues and 228 have been closed. On average issues are closed in 57 days. There are 3 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of coraza is v3.0.0

            kandi-Quality Quality

              coraza has no bugs reported.

            kandi-Security Security

              coraza has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

            kandi-License License

              coraza is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              coraza releases are available to install and integrate.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
            Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of coraza
            Get all kandi verified functions for this library.

            coraza Key Features

            No Key Features are available at this moment for coraza.

            coraza Examples and Code Snippets

            No Code Snippets are available at this moment for coraza.

            Community Discussions


            Ansible Update multiple firewall rules on Vyos
            Asked 2022-Apr-11 at 02:35

            I've been trying to create a playbook that I can run periodically to go through all my Vyos firewall rules and ensure the "log enabled" command is present, just in case someone forgets to add logging to a firewall rule. I've found the vyos.vyos.vyos_firewall_rules module which I think will be perfect for what I need to do.

            The only problem is, is that this module requires you input the rule set name and rule number of each firewall rule that you want to update. However in my case, I want this to be done automatically and Ansible to go through each firewall rule set and associated rules that are present, and ensure logging is enabled on each rule. Something like this is what I need:



            Answered 2022-Apr-11 at 02:35

            You can create the dictionary first



            Error 2002 or 2013 when connecting to my MariaDB database on Cloud SQL
            Asked 2022-Apr-08 at 15:21

            I´m experiencing some kind of network issue when connecting to my MariaDB remotely, which is hosted on a CloudSQL instance (nevertheless, I think that this is unrelated).

            When I'm trying to connect through mysql.exe or mariadb.exe from my installation of mariaDB:



            Answered 2022-Apr-08 at 15:21

            Cloud SQL supports MySQL, Postgres, and SQL Server engines, but not MariaDB.

            Additionally, you tested telnet x.y.z.a 5432, but the port for Cloud SQL MySQL instances is 3306. (5432 is the port for Postgres).

            You should verify which type of Cloud SQL instance you have created, and that you are using the right cli to connect with it.



            problem with port 587 how enable this for send email
            Asked 2022-Mar-18 at 10:39

            hi I'm trying send email , but I just get this error :



            Answered 2022-Mar-18 at 10:39

            If you are calling from your application to the gmail server. That would be an outbound rule so you need to add a outbound exception to the firewall.



            What does wg-quick nftables rules do?
            Asked 2022-Jan-24 at 00:45

            When I add a wireguard interface via wg-quick up wg0, wg-quick sets up the following nftable rules. What are these doing and why are they needed?

            Here are some example rules for ipv4:



            Answered 2022-Jan-24 at 00:45

            The wg-quick script sets up these rules only when you configure the AllowedIPs of a WireGuard peer to include /0 -- aka "all addresses" or the "default route" for an address family ( for IPv4 and ::/0 for IPv6).

            Using a tunnel like WireGuard for a default route requires some tricks to work correctly in most scenarios. The main trick wg-quick uses is to put the new default route into a custom routing table, while adding policy routing rules with a firewall mark to overide only the default route of the main table. This is the purpose for the route and policy rules you'll see wg-quick set up in this case:



            How to enable the TLS Inspection and IDPS premium features of Azure Firewall Policy
            Asked 2022-Jan-21 at 12:03

            I have created an Azure Firewall Policy with Premium tier using the following terraform code:



            Answered 2022-Jan-21 at 12:03

            As provided in this Microsoft Documentiation ARM template , you will have to declare the TLS inspection and IDPS in azurerm_firewall_policy in tls_certificate block and intrusion_detection block .

            ARM Template:



            Can ssh to GCP Private instance but cant access application interface through cloud shell
            Asked 2022-Jan-19 at 12:17

            Here is what i have:

            • GCP instance without external IP (on VPC, and NAT), and it accepts HTTP HTTPS requests
            • firewall allows ingress TCP for and also for IAP's IP on all ports for all instances

            I ssh to the instance via IAP and run the application in the terminal on port 5000 and host and leave the terminal hanging, but when I connect in parallel through cloud shell and ssh to this instance through IAP, and then click on web preview on port 5000, I get "Couldn't connect to a server on port 5000". I have said that it could be a firewall rule blocking IAP, so that's why I gave access to all ports for IAP (for testing)

            P.S: the process has been done on a VM with external IP and it got validated ( but without the need to connect to cloud shell to do web preview, I checked the UI with IP:port in the browser )

            What did I miss?



            Answered 2022-Jan-19 at 12:17

            You may be following the guide on Building Internet Connectivity for private VMs and this part on Configuring IAP tunnels for interacting with instances and the use of TCP Forwarding in IAP. By Tunneling other TCP connections:

            "The local port tunnels data traffic from the local machine to the remote machine in an HTTPS stream. IAP then receives the data, applies access controls, and forwards the unwrapped data to the remote port."

            You can create an encrypted tunnel to a port of the VM instance by:



            Correct syntax for modsecurity rules for Wordpress / Elementor false positives
            Asked 2022-Jan-14 at 22:51

            I'm getting tripped by my WHM ModSecurity using OWASP3 rules.

            I'd like to create a custom rule to the Rules List in Home>Security Center > ModSecurity Tools>Rules List following these exclusions:



            Answered 2022-Jan-14 at 22:51

            Core Rule Set Dev on Duty here. As the list of exclusions you gave comes from someone else's blog post it's probably best to ignore them. They disable some key functionality of the Core Rule Set (the 9xxxxx rules you're using is the OWASP Core Rule Set) so it's best not to apply those rule exclusions unless you're certain you know what you're doing and why those exclusions are required.

            The three entries from the "HitList" that you quoted: are you certain those are the result of known good traffic? Are those definitely from when you were trying to update a page and you got 403 errors? If you're sure those are genuine false positives (and not attacks) then let's continue…

            False positive #1
            • The rule causing the false positive: 921110
            • The location in question: /wp-admin/post.php
            • The variable causing the false positive: ARGS:content

            Applying a rule exclusion means poking a hole in your WAF's security. We want to try and be as specific as possible so that we make only the smallest hole necessary. We just want to let through the transactions that are being blocked in error and nothing more. We don't want to open a large hole and present an opportunity for attackers to get through.

            With that in mind, let's try taking the following approach: let's exclude only the variable in question (ARGS:content) and exclude it only from the rule causing the issue (921110) and only for the location we've seen the problem occur at (/wp-admin/post.php).

            Putting all that together looks like so:



            GCP firewall rule for tcp port are not working
            Asked 2022-Jan-13 at 03:08

            I've a VM on which I installed postgres, now I'm trying to connect the this PG from outside, I created a firewall rule that opens the 5432 port to any source IP like below

            My instance has the rule

            But when I try to check if the port is open it fails for me



            Answered 2022-Jan-13 at 03:08

            Connection refused means you can initiate a TCP connection but no process is listening on the port, so the connection attempt is refused. This means the firewall is probably not the problem. A firewall problem usually results in a Timeout error.

            Edit the postgresql.conf configuration file:



            how make instance group members work behind behind loadbalancer only
            Asked 2022-Jan-12 at 06:52

            I am able to make work the backend service as an instance group - if i enable the "Allow http access" enabled while creating the members in the instance group.

            However i want to disable this and make the network work only from the loadbalancer(external ip). However it is not working. The way I did was to define a firewall rule in the subnet where the instance group is there, such that the destination is the network tags defined for the instance group members

            settings link as iamge

            the source is dfined as the ip of the load balancer as a range.



            Answered 2022-Jan-11 at 22:55

            Where you looking is fine, you can do it. The steps are, as I suggested in my comment a little bit more, I will resume them in this list, and let you the link of a qwiklab, you can check the steps there with the code to do it by yourself.


            1. Create the instances or instance group with the corresponding healtcheck.
            2. Configure the Load balancer
            3. Set the traffic to the new loadbalancer and build the proxy.
            4. Create HTTPS Load Balancer and send the traffic to the Proxy.


            I think that the link is creating instance by instance, but the steps should be the same for an instance group.



            Keep efimeral external IP but disable external HTTP request and keep internals on Google Compute Engine
            Asked 2021-Dec-16 at 08:55

            I have an App on GCE that needs to have "internet" connection, but I don't want it to be accessible externally, but only by its internal IP (HTTP) by others service (others GCE and Cloud Run instances on serverless VPC).

            How can I disable the external without removing the external IP? Thanks



            Answered 2021-Dec-15 at 09:02

            There are two implied firewall rules in gcp with lowest priority. You cannot delete these.

            • Allow all egress traffic (this will allow your instance to access the internet)
            • Deny all ingress traffic (this blocks your instance to be accessible from anywhere)

            Solution - You can create a firewall rule to allow ingress traffic only from internal vpc network on TCP port 80.

            1. Select your instance and click on Edit.
            2. In Networking column, remove http-server and https-server tags if present and add your own tag e.g "my-app" and save. We will allow http traffic in our own firewall rule.
            3. Go to VPC network. Select Firewall. Create a firewall rule to allow ingress traffic with target tag as "my-app" and source as CIDR IP range of your vpc network or subnet with tcp port 80. This rule will allow only internal HTTP traffic only from vpc network.


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install coraza

            You can download it from GitHub.


            Contributions are welcome. There are many TODOs, functionalities, fixes, bug reports, and any help you can provide. Just send your PR.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone corazawaf/coraza

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Reuse Pre-built Kits with coraza

            Consider Popular Firewall Libraries


            by evilsocket


            by fail2ban


            by screetsec


            by Screetsec


            by SpiderLabs

            Try Top Libraries by corazawaf


            by corazawafGo


            by corazawafGo


            by corazawafGo


            by corazawafHTML


            by corazawafGo