Core Rule Set (CRS)
We provide Core Rule Set (CRS) consulting, integration, tuning, maintenance, and technical support. We help organizations deploy and operate CRS rules with a compatible web application firewall engine, with attention to legitimate application traffic and the investigation of security events.
Our services focus on ruleset behavior, application-specific tuning, test coverage, and change management. We coordinate with your web platform and security teams to define how the rules will be introduced, monitored, and maintained as applications evolve.
CRS is a ruleset that depends on a compatible inspection engine and its configuration. Rule matches need context, and effective tuning requires knowledge of both the rules and the application's request behavior.
We help your team build a repeatable process for reviewing alerts and changing configuration without losing track of why an adjustment was made.
What we do
01 / 10
Review how CRS fits into the selected web application firewall architecture. We assess engine compatibility, application request patterns, current controls, and operational responsibilities before defining the initial configuration and rollout approach.
02 / 10
Configure the selected CRS release in the chosen inspection environment. We verify rule loading and required settings, test sample requests, and document the configuration so that operators can understand and reproduce the deployed behavior.
03 / 10
Help your team select an initial inspection posture and a method for adjusting it. We review anomaly scoring, paranoia levels, and enforcement behavior in the selected release, then validate the effect against representative legitimate and test traffic.
04 / 10
Analyze rule matches affecting legitimate application requests. We identify the relevant fields and conditions, implement targeted exclusions where appropriate, and test the adjustment so that exceptions remain understandable and limited to the intended application behavior.
05 / 10
Test CRS behavior against the application's normal user journeys and data formats. We review requests such as forms, uploads, and API payloads to identify tuning needs and parser dependencies before broader enforcement is introduced.
06 / 10
Help operators distinguish rule activity that needs investigation from recurring application-related noise. We organize event views and triage procedures that retain matched-rule context, anomaly information, and the request evidence needed for a meaningful review.
07 / 10
Introduce ruleset changes through measurable stages. We assess inspection overhead, event volume, and legitimate traffic behavior, then help define deployment and rollback procedures so that operational effects can be reviewed before wider enforcement.
08 / 10
Keep local tuning and upstream ruleset changes understandable over time. We compare relevant changes, review exclusion compatibility, and run regression tests so that upgrades preserve intended inspection behavior while bringing forward appropriate improvements.
09 / 10
Get help with unexpected blocks, excessive false positives, rule compatibility problems, scoring questions, missing events, and upgrade regressions. We examine the available evidence, coordinate investigation across the relevant components, and help your team identify corrective actions.
Support arrangements define the covered environment, service hours, communication channels, priorities, and escalation process. This gives your team a clear route for requesting assistance and following an issue through investigation, validation, and closure.
10 / 10
Build practical understanding of CRS configuration, anomaly scoring, paranoia levels, exclusion design, event investigation, and ruleset maintenance. We tailor sessions to the environment and the responsibilities of the people developing, administering, and supporting it.
Workshops can use your configuration, representative examples, and agreed operating scenarios. Documentation and runbook walkthroughs help your team apply the knowledge after the engagement.
How we engage
You may need a technical assessment, a defined implementation project, help with a recurring problem, or ongoing operational assistance. We offer consulting, project delivery, and support arrangements built around that need.
We can work alongside your internal team or take responsibility for agreed activities. The scope sets out the environment, dependencies, access, deliverables, and responsibilities, with coverage and response targets defined in the service agreement. Ongoing engagements can include scheduled health reviews, maintenance planning, and progress reporting.
01
Assessments, architecture reviews and technical guidance.
02
Implementation, migration and upgrade projects with handover.
03
Incident investigation and resolution guidance under agreed coverage.
04
Ongoing administration for the activities assigned to us.
We treat each exclusion as a documented change that needs a reason and a test. Application workflows and agreed security cases are checked together, helping your team maintain a useful balance between inspection coverage and the ability of legitimate users to complete their tasks.
We agree the work and acceptance checks with your team, validate changes in a suitable environment, and document the outcome. Clear handover makes the configuration, operating procedures, and next actions easier to maintain after delivery.
Versions below were confirmed against upstream release information on 15 October 2026. We reconfirm them at the start of each engagement.
Standard support is delivered in business hours, Monday to Saturday, India Standard Time. Coverage hours, response targets and escalation steps for each severity are defined in the service agreement. Upstream response times are outside our control.
Get in touch
Deploying CRS, reviewing a noisy ruleset, or preparing an upgrade? Share your inspection engine, application request patterns, and current rule-tuning challenges so we can plan the required services.
Core Rule Set and CRS are trademarks of their respective owners and are used here only to describe the software we support. We are an independent service provider and are not affiliated with, endorsed by or sponsored by the Core Rule Set project or OWASP.
Copyright 2026 AMNEX INFOTECHNOLOGIES PRIVATE LIMITED.
