Updated: 18 November 2026
DPDP Rule 6 requires reasonable security safeguards, including access limited to authorised persons, one-year audit log retention, and the ability to detect and reconstruct unauthorised access. For a firewall, this translates to six evidence artefacts a Data Protection Officer should be able to produce on demand: rulebase register, change log, access matrix, retention proof, detection log and reconstruction workflow.
Written for CISOs, Data Protection Officers, Heads of Information Security and Compliance leads in Indian enterprises approaching the 13 May 2027 DPDP hard-enforcement deadline.
A Data Protection Board inspection team, an internal audit committee or an external DPDP readiness assessor will not ask about the firewall product first. They will ask a version of this:
Show me evidence that access to the network segment carrying personal data was, over the last twelve months, limited to authorised persons only, and that any deviation was detectable and reconstructable.
Producing that evidence, from a firewall estate that has grown organically over five to seven years of undocumented rule additions, is difficult. Producing it from a firewall estate that has been operated as a documented, curated discipline is a routine exercise. The gap between the two states is the difference between an audit that concludes cleanly and one that turns into a finding with a compliance clock attached.
Rule 6 does not care about the product name. It cares about the evidence. This piece walks through what evidence, in what form, for a firewall.
The relevant Rule 6 provisions, paraphrased for operational orientation (the definitive text sits in the DPDP Rules 2025 notification):
Confidentiality of personal data through appropriate technical and organisational measures, including encryption. For a firewall, this covers VPN tunnels (IPsec, TLS 1.2 or above) and any personal data crossing the firewall in transit.
Access limited to authorised persons. The firewall's rulebase is the technical expression of this control. Every rule that permits access to a segment carrying personal data must be traceable to a person or a role authorised to have that access.
Continuous audit logs enabling detection, investigation and prevention. Retention of at least one year is stated in the Rules; longer retention may apply where sectoral regulators (RBI, SEBI, IRDAI) require it.
Means to investigate and report a breach. The firewall logs and configuration history must be sufficient to reconstruct what happened, in enough detail to file the CERT-In six-hour report and the DPDP Data Protection Board notification (without delay plus 72-hour follow-up).
Reasonable contractual safeguards with processors. When a managed operator runs the firewall, the contract must include DPA clauses, right to audit, breach pass-through obligations, and exit provisions.
Five provisions. Each translates to specific evidence artefacts.
Compiled from live audits and internal DPO reviews we have supported across Indian BFSI, ITeS and manufacturing customers.
| Artefact | What It Contains | Rule 6 Provision Satisfied |
|---|---|---|
| Rulebase register | Every active firewall rule with purpose, owner, review date, creation date | Access limited to authorised persons |
| Change log | Every rule addition, modification or deletion in the last 12+ months, with reviewer and rationale | Access limited to authorised persons; reconstruction |
| Access matrix | Which named individuals (or roles) have permission to modify the firewall, with rotation history | Access limited to authorised persons |
| Retention proof | Documentation of log storage location, retention window, integrity controls, and last successful retrieval test | Continuous audit logs (one-year minimum) |
| Detection log | IPS event history, threat intelligence subscriptions, tuning history, and false-positive suppression rules | Detection of unauthorised access |
| Reconstruction workflow | The documented process by which a suspected breach is investigated, with timing that supports the six-hour CERT-In clock and 72-hour DPDP clock | Investigate and report a breach |
A DPO who can produce all six inside an audit meeting has done most of the operational work of DPDP Rule 6 for the firewall estate.
The rulebase register is the single artefact that decides most audit conversations. A rulebase where every entry has a stated purpose, a named owner and a next-review date is defensible. A rulebase that is a sequential list of IP ranges and ports without explanation is not.
A well-maintained register captures:
Rule identifier and position in the rulebase.
Source and destination in named terms (not just IP ranges: "Client A dev VLAN to Client A production database", not "10.14.3.0/24 to 10.19.7.42").
Ports and protocols allowed.
Purpose statement: what business need this rule serves.
Rule owner (person or role accountable for the rule's continued existence).
Creation date, last review date, next review date.
Change history: every modification since creation, with date and reviewer.
Sunset date where the rule is time-bound (contractor access, temporary vendor).
Under Managed Firewall Services on Cisco Secure Firewall, this register is maintained as an operational artefact, exported quarterly for internal audit, and reviewed against the actual rulebase state to catch drift. Discrepancies between the register and the running configuration are themselves flagged for investigation.
Rule 6 states one year as a minimum. Sectoral regulators often require longer: RBI expectations for BFSI transaction logs run to several years, SEBI CSCRF for capital markets typically five years, IRDAI similar for insurance. The one-year floor sits under all of them.
Log retention as an evidence artefact requires four sub-elements:
Storage location and controls. Where the logs sit, who can access them, what integrity controls apply (write-once storage, hash-verified archives, tamper detection).
Retention window per log source. Firewall event logs, IPS logs, admin access logs, configuration change logs. Each may have a different retention window based on cost and regulatory driver.
Retrieval test evidence. Regular tests that the logs can be retrieved and are readable. A log archive that cannot be retrieved on demand fails the "available" limb of ALCOA+ and the substance of Rule 6.
Time-source consistency. All log-generating systems synchronised to a common trusted time source (NTP against reliable stratum-1 sources). Auditors notice when timestamps do not align across systems.
Under a Managed Firewall Services contract, retention is configured at onboarding against the customer's regulatory and audit calendar, the retrieval test is scheduled quarterly, and the retention documentation is refreshed as part of standard operational reporting.
Rule 6's "access limited to authorised persons" is not just about network traffic. It applies to the firewall itself. Every modification to firewall policy must be attributable to a named person with the authorisation to make that change.
This forces four practical disciplines:
Named-user administrative access, not shared accounts. Every admin session is traceable to an individual.
Multi-factor authentication on firewall management access. Cisco Duo integration on the Firewall Management Center (FMC) is the standard pattern.
Every change reviewed before it lands. The reviewer is a second person, not the same person making the change.
Every change logged with rationale. The what and the why, captured at the time of change, not reconstructed later.
Managed Firewall Services enforce all four through the ticket workflow: no change happens without a ticket, no ticket closes without reviewer sign-off, all administrative access is through Duo-protected named accounts, and the change history is part of the standard evidence pack.
Detection without reconstruction is useless in an audit. Reconstruction without detection is impossible.
Detection is the IPS event stream, the threat intelligence feeds (Cisco Talos for Cisco Secure Firewall), the log-based anomaly alerts, and the tuning discipline that keeps false positives suppressed without disabling signatures. The detection log is the evidence that unusual events were observed and classified.
Reconstruction is the ability to answer, at the moment an incident is detected, four questions inside the CERT-In six-hour window: what happened, when did it happen, what data was in the affected path, and what containment action was taken.
Firewall logs feed both. IPS event logs, connection logs, authentication logs, DNS logs, VPN session logs. Aggregated into a SIEM (Splunk, Sentinel, QRadar, or Cisco XDR), correlated, and queryable. A managed contract typically includes SIEM integration or standalone log aggregation, retention as above, and a documented reconstruction workflow that has been tested against tabletop scenarios.
The reconstruction workflow itself is an evidence artefact. Auditors ask to see the workflow, not just the tools. A workflow document that has been reviewed in the last quarter and tested in the last year is a defensible answer.
Rule 6 is producible in-house. It requires a firewall administrator with time to maintain the rulebase register, log retention discipline that survives when the administrator is on leave, change control that never bends under production pressure, and detection tuning that keeps pace with the threat landscape. Enterprises with the headcount and the operational maturity to do all four continuously can produce the six evidence artefacts on demand.
Where the in-house model breaks, and it usually does, is under sustained delivery pressure.
The rulebase register goes six months without an update. Retention documentation drifts. Change control gets short-circuited during a product launch. The DPO discovers this the week before the audit and spends a fortnight reconstructing what should have been continuous.
Managed Firewall Services replace episodic effort with operational rhythm. The register updates weekly. Retention gets a monthly integrity check. Change control cannot be bypassed because the workflow is the only path to a change. The six evidence artefacts are produced continuously, not reconstructed for the audit.
For an enterprise approaching the 13 May 2027 DPDP hard-enforcement deadline, the operational rhythm question is what to plan for. The audit will come. The evidence needs to be waiting.
Two hours with your CISO, DPO and Head of Network Security. We snapshot your Cisco Secure Firewall or ASA configuration, run it against the six evidence artefacts, and hand you a written finding by end of week. What is defensible today. What is missing. What can be closed inside sixty days.
Proactive is a Cisco Penta-Preferred Partner under the Cisco 360 Partner Program.
Disclaimer: Regulatory references (DPDP Act, DPDP Rules 2025, CERT-In Direction 2022, RBI Cyber Security Framework, SEBI CSCRF, IRDAI guidelines) in this piece are drawn from currently published guidance and are for operational orientation, not regulatory or legal advice. Compliance posture for any specific enterprise depends on entity classification, data processing scope, sectoral regulator overlay and audit interpretation. A qualified privacy lawyer, DPO or regulatory adviser is the definitive voice on DPDP obligations.
We'll get back to you shortly.