The national legal framework
Cybersecurity compliance in India combines technical resilience with legal duties that differ by organisation and activity. The Information Technology Act provides the foundation for CERT-In directions and other security powers, while banking, securities, insurance, telecommunications and critical infrastructure may be subject to additional sectoral requirements. A general security standard or vendor certificate does not establish compliance with every applicable rule. The legal assessment should identify the regulated entity, systems, data, outsourced services and incident categories before selecting controls, reporting channels and contractual responsibilities.
CERT-In’s April 2022 Directions impose specific obligations on covered entities, including reporting specified cyber incidents within six hours of noticing them or being informed about them, together with logging and other requirements. The direction, official FAQs and later instruments should be read together for scope and implementation. A police complaint, customer email or notification to a foreign regulator does not automatically discharge the CERT-In duty. Sector regulators may impose separate obligations, and the future DPDP breach framework should be distinguished from duties already operating as of the edition date.
An incident-response plan should assign responsibility for technical containment, evidence preservation, legal classification, regulatory reporting and communications. It should work outside normal office hours and allow an initial report to be supplemented as facts become clearer where the applicable process permits. Preserve logs and forensic material without unnecessarily expanding access to sensitive information. Supplier agreements should address escalation, cooperation, audit evidence and the organisation’s ability to meet its own deadlines. After an incident, record the root cause, remediation and lessons learned. Neither paying a ransom nor obtaining a clean technical scan necessarily resolves legal exposure, notification obligations or the need to investigate affected data and systems.
The Rajasthan context
Business and commercial activity
Rajasthan public procurement has a specific statutory framework in the Transparency in Public Procurement Act, 2012 and Rules, 2013. The Finance Department’s guidance expressly directs users to the legislation. A bidder should review eligibility, evaluation, security and challenge procedures from the actual tender rather than assume general commercial negotiation rules apply.
For private projects, separate the corporate vehicle from land, sector and incentive approvals. Public-contract claims should preserve clarifications, award terms, measurements and authorised variations. A procurement challenge and a post-award payment dispute may require different procedures; identify the stage and remedy before issuing a demand or invoking an arbitration clause.
Exemptions and later procurement amendments must be checked for the procuring entity and transaction.
Local points to investigate
- Review tender and statutory procedures together
- Preserve evaluation and variation records
- Distinguish bid challenges from payment claims
Acts, rules & official sources
Information Technology Act, 2000
Provides electronic transaction, computer-security, confidentiality and intermediary frameworks.
Read the official source ↗Applies according to entity and incident categories; read with official clarifications and later instrumentsCERT-In Directions under section 70B(6), 28 April 2022
Sets covered entities’ incident reporting, logging, time synchronisation and specified customer-information obligations.
Read the official source ↗Explanatory guidance read with the binding directions and subsequent clarificationsCERT-In official FAQs on Cyber Security Directions
Explains the scope and implementation of the April 2022 cybersecurity directions.
Read the official source ↗Consent-manager phase follows in November 2026; core duties follow in May 2027 under the published scheduleDPDP commencement notification — G.S.R. 843(E), 13 November 2025
Specifies immediate, one-year and eighteen-month commencement groups for the Act.
Read the official source ↗State public procurementRajasthan Finance Department: procurement guidance
Official guidance under the Transparency in Public Procurement Act, 2012 and Rules, 2013.
Read the official source ↗State public procurement lawRajasthan Transparency in Public Procurement Act, 2012
Statutory principles and procedures for covered state procurement.
Read the official source ↗Different incident duties can run in parallel; do not assume a single report satisfies all regulators or contractual obligations.
Preparing the matter
- Identify applicable CERT-In and sector-specific duties.
- Maintain an incident classification, escalation and reporting matrix.
- Preserve logs, forensic evidence and a clear response chronology.
- Test supplier notification and after-hours response arrangements.
District and court information
Use the district profile for official administrative identity and local references. The competent court, regulator or tribunal depends on the issue and jurisdictional rules rather than the district name alone.
Explore districts in Rajasthan ↗Questions & scope
Does reporting a cyberattack to police satisfy CERT-In requirements?
Not automatically. CERT-In reporting is a separate legal process for covered entities and incidents, and sectoral or contractual notifications may also be required.
Does a state guide create a separate rule for every subject?
No. Many subjects are governed principally by central legislation. The local section identifies related institutions and state context; it does not imply that a different substantive rule exists in every state.
This edition provides general legal information and selected official sources. Applicable amendments, commencement, territorial scope, court practice and the facts must be checked for an actual matter.

