Overview

Demonstrating the effectiveness of cybersecurity controls is an important part of security audits, regulatory reviews and internal compliance assessments.

The GAJWAF Compliance Reporting Playbook provides a structured approach to generating, interpreting and presenting security reports that accurately reflect the protection delivered by GAJWAF.

The playbook helps administrators and security analysts prepare audit-ready evidence based on actual security events, enforcement actions and application protection configurations.

The guiding principle is simple: Report What It Did. Nothing More.

Rather than making broad claims about security effectiveness or compliance certifications, the playbook emphasizes accurate reporting, traceable evidence and clear distinctions between observed threats and actively blocked attacks.

What You'll Learn

This playbook covers four essential stages of compliance reporting.

Step 1: Prepare for Compliance Reporting

Before generating a report, verify that the relevant applications are configured appropriately and that security events have been collected throughout the required reporting period.

The guide explains how to:

  • Confirm whether protected applications are operating in Block or Detect mode.
  • Verify that security event collection is enabled.
  • Ensure the reporting period contains sufficient event data.
  • Identify gaps in event collection or enforcement.
  • Clearly document periods during which attacks were observed but not blocked.

Step 2: Generate Security Reports

Learn how to generate reports using GAJWAF's reporting capabilities.

The playbook explains how to:

  • Select the exact reporting period requested by an auditor.
  • Choose the applications and websites included in the audit scope.
  • Generate reports in PDF, HTML or CSV format.
  • Configure scheduled reports for recurring compliance requirements.

Configuration Location: Settings → Reports & Compliance

Step 3: Interpret Security Events Accurately

Understanding the difference between detection and enforcement is essential for reliable compliance reporting.

The guide explains how to interpret GAJWAF security actions, including:

  • Blocked: Requests actively denied or blocked by security controls.
  • Observed: Suspicious requests detected and logged without being blocked.
  • Throttled: Requests restricted through rate-limiting controls.
  • Challenged: Requests subjected to browser verification.
  • Response Masked or Blocked: Responses modified or blocked by data protection controls.
  • Allowed: Requests permitted to proceed.

The playbook also explains how to present evidence relating to application attack prevention, bot mitigation, API validation and data leak prevention.

Importantly, it emphasizes that security reporting must distinguish between supporting specific compliance controls and claiming certification against a standard.

Step 4: Deliver Audit Evidence

Learn how to prepare the final report package for auditors and compliance teams.

The process includes:

  • Exporting the report in the required format.
  • Verifying that all figures correspond to actual security events.
  • Including relevant deployment-hardening evidence.
  • Maintaining a copy of the report in the organization's compliance records.
  • Completing the report review and approval process.

Why This Playbook Matters

Security reporting should provide clear, verifiable evidence of the controls operating within an organization's environment.

Following this playbook helps organizations:

  • Produce accurate security reports for internal and external audits.
  • Demonstrate which applications are protected by GAJWAF.
  • Distinguish between attacks detected and attacks actively blocked.
  • Present evidence of application security, bot protection, API validation and data leak prevention.
  • Maintain traceability between reported figures and actual security events.
  • Avoid unsupported compliance or certification claims.
  • Establish consistent reporting procedures for recurring audits.

Report Validation and Sign-Off

The playbook includes a report sign-off checklist to verify that:

  • The report covers the correct reporting period.
  • All relevant applications are included.
  • Block and Detect mode periods are accurately represented.
  • Reported figures are supported by actual security events.
  • Compliance claims are limited to supported controls and verified certifications.
  • Required supporting evidence has been included.

A report-record template is also provided to document the auditor, reporting period, application scope, referenced controls, delivery format and review details.

Download the Playbook

Document: GAJWAF Playbook – Compliance Reporting
Document Version: 1.0
Document Type: Operations and Compliance Reporting Playbook
Publication: October 2026
Pages: 6
Intended Audience: GAJWAF Administrators and Security Analysts

Attachment: GAJWAF_Playbook_Compliance_Reporting.pdf

Download the attached PDF for detailed reporting procedures, event-action definitions, compliance evidence guidance and the report sign-off checklist.

Related Documentation

For additional guidance, refer to:

Technical Support

For assistance with GAJWAF reporting, audit evidence or security configuration, contact GajShield Technical Support or your authorized GajShield partner.

Website: https://www.gajshield.com

GAJWAF: Different Applications. Different Protection. Shared Risk Intelligence.