01
Observed inventory
Identify scripts and providers captured on monitored pages.
Bring browser evidence into your next review.
Client-side compliance reporting brings observed scripts, authorization records, findings and configured controls into a reviewable report. Use it to support PCI DSS, GDPR and ISO 27001 work alongside your organization's wider evidence and assessment processes.
Our approach
Observe. Review. Export.
Connect captured browser activity with deliberate decisions and supporting records.
02
Recorded decisions
Review authorization, business justification and vendor assessment status.
03
Configured controls
Inspect supported policy and monitoring context alongside findings.
Framework context
Evidence for the review at hand.
Explore browser-side records in the context of the framework your team is reviewing.
Compliance frameworks
Payment-page security
PCI DSS v4.0.1
Support payment-page script management and change-detection reviews.
- Review context:Focus on browser-side workflows relevant to 6.4.3 and 11.6.1.
- Supporting records:Observed scripts, authorization and justification, findings and monitoring context.
- Browser-side support:Review configured payment-page scope and export available technical records.
Privacy accountability
GDPR
Bring observed browser activity into privacy and data-flow reviews.
- Review context:Interpret the technical context alongside purposes, legal bases and wider privacy records.
- Supporting records:Observed providers, resources, destinations and available consent context.
- Browser-side support:Use runtime observations to investigate differences from expected website behavior.
Information security
ISO/IEC 27001:2022
Contribute browser-side records to the organization's ISMS.
- Review context:Review client-side assets, supplier context, configuration and monitoring processes.
- Supporting records:Provider review status, resource inventory, findings and configured policies.
- Browser-side support:Export supporting browser records without treating them as a complete ISMS assessment.
Browser observations
Keep browser context current.
Review new observations alongside existing decisions as the monitored website changes.
Resource observations
InventoryInspect supported resources and browser activity captured by monitoring.
Change findings
InvestigationReview observed changes and findings in the configured monitoring scope.
Review records
Decision contextKeep authorization, vendor assessment and current status available for review.
Network context
DestinationsInspect observed destinations alongside configured network boundaries.
Browser observations
cellwall.io
Review context
Recorded
Review context
marketing-pixel.js
Script updated
Event recorded
Example event
Ready for review
Ongoing review
Review what changed.
New browser observations give reviewers context to revisit a resource, finding or configured policy.
Observed change
Investigate new resources and supported behavior changes in captured activity.
Deliberate follow-up
Review findings and decide whether supported controls or organizational records need updating.
Reporting & exports
Export a supporting evidence report.
Prepare available technical records for internal review and assessor conversations.
Script authorization context
Review observed scripts alongside recorded authorization and business justification.
Framework-specific PDF reports
Generate PCI, GDPR or ISO reports from the selected project's available records.
Findings and control context
Bring monitoring observations and configured policy status into the review.
Example PCI report workflow. Results depend on configured scope and available observations.
Review workflow
Keep the assessment in context.
Use browser records as input to the organization's wider review process.
PCI DSS
Script review
Review authorization and justification with the observed payment-page inventory.
GDPR
Privacy review
Compare observed browser activity with privacy records maintained by your organization.
ISO 27001
Control review
Use browser monitoring and policy context within the wider ISMS.
Evidence mapping
Connect the record to the review.
These are browser-side contributions, not complete requirement or framework coverage.
| PCI DSS v4.0.1 | 6.4.3Payment-page script management | Inventory, authorization and business justification |
| PCI DSS v4.0.1 | 11.6.1Payment-page change detection | Configured scope, observations and findings |
| GDPR | Privacy reviewBrowser-side data governance | Provider, destination and runtime context |
| ISO/IEC 27001:2022 | Asset reviewClient-side software assets | Observed resource and provider inventory |
| ISO/IEC 27001:2022 | Control reviewBrowser monitoring and configuration | Policies, findings and supporting observations |
Explore the supporting workflows
- PCI DSS payment-page evidence
- GDPR browser evidence
- ISO 27001 browser security
- Browser policy enforcement
Framework guidance
Content reviewed: 5 September 2026
Reporting questions
What the report can help you establish.
What is client-side compliance reporting?
It organizes observed browser resources, recorded decisions, findings and configured controls into supporting technical evidence.
Which reports can I download?
The platform provides project-level PCI, GDPR and ISO PDF report downloads based on available records.
Does the report certify compliance?
No. Scope, implementation, organizational processes and qualified assessment remain necessary. Browser evidence covers only part of that work.
Are permissions or legal decisions applied automatically?
Observed activity informs review. Teams configure supported policies and record decisions; a report does not determine legal bases or automatically establish compliance.
How should exported evidence be handled?
Apply your organization's retention, access and evidence-handling requirements to downloaded reports and supporting records.
How should I use the report in an assessment?
Check monitored scope, available observations and current decisions, then combine the export with organizational records and the assessor's evidence requirements.
Assessment preparation
Bring the browser record to the conversation.
Explore the reporting workflow or discuss the evidence your team needs.
Browser-side evidence supports review. It does not certify compliance or replace legal advice or an organization's wider controls.