in forcenot yet in forceblocked by a courtproposedno longer in force
Privacy law6 instruments, 6 in force
Research summary (222 words)
Bahrain's Personal Data Protection Law (Law No. 30 of 2018, PDPL), read in full at primary source, was the first standalone data-protection statute in the Gulf. Its most distinctive structural feature: biometric data is not part of the "Sensitive Personal Data" definition, but it gets its own, separate, and arguably stronger control.
Article 15's "Prior Authorisation" provision prohibits, without the Personal Data Protection Authority's (PDPA) prior written authorisation, automatic processing of biometric data necessary for identity verification, and separately, visual-recording processing used for surveillance purposes, a heavier gate than mere consent, distinct from the Sensitive Personal Data consent rule in Art. 5.
Because biometric data sits outside the Sensitive Personal Data definition, Art. 5(3)'s publicly-available-data consent exemption plausibly does not reach the Art. 15 prior-authorisation requirement at all, even for data the individual made public. Cross-border transfer is a prohibition-with-listed-exceptions structure (Arts. 12-13), read as stricter than the carried moderate seed. The base Law's own text contains no General Data Protection Regulation (GDPR)-style incident-notification duty with a fixed timeline.
Bahrain arms a private plaintiff: Art. 57 lets a party who suffers damage from a Data Controller's processing, or from a Data Protection Guardian's violation of the Law, claim compensation directly, without prejudice to the Civil Law. Roughly ten Ministerial Resolutions (Orders No. 42-51 of 2022) supply substantial further operative detail; their content is not described here.
Art. 15 prohibits, without the PDPA's prior written authorisation, five listed operations including automatic processing of biometric data necessary for the verification of an individual's identity (Art. 15(2)), and processing by means of visual recording used for surveillance purposes (Art. 15(5)).
This sits in its own category distinct from Sensitive Personal Data (Art. 5) and genetic data (Art. 15(3)), gated by a heavier control than mere consent: ex ante regulatory authorisation before processing may begin at all. No modality-specific (voice or face) language was found.
Art. 15(2)'s framing is keyed to a verification use case; it is a genuine, unresolved textual question whether a biometric identifier created for a non-verification purpose (profiling, search, watchlist matching) falls within Art. 15(2) at all, or falls entirely outside both the Sensitive Personal Data consent rule and the Art. 15 prior-authorisation rule. Art. 15(5) independently reaches a faceprint derived from CCTV or similar recorded video used for surveillance. No retention or destruction duty specific to biometric data was found.
The Personal Data Protection Law is Bahrain's comprehensive, consent-centric statute with enumerated grounds. Processing generally requires the Data Subject's consent or a listed alternative basis. A Controller/Processor structure is present, alongside a "Data Protection Guardian" role, Bahrain's DPO-equivalent. The Personal Data Protection Authority (PDPA), established by Art. 27, supervises compliance.
Roughly ten Ministerial Resolutions (Orders No. 42-51 of 2022) supply substantial operative detail; their content is not described here.
Art. 12 prohibits transfer of personal data outside Bahrain except to a country on a PDPA-published adequacy whitelist (published in the Official Gazette), or under a case-by-case PDPA authorisation based on an adequacy assessment considering the data's nature, origin and destination, and relevant international agreements.
Art. 13 lists exemptions allowing transfer to a non-adequate destination without going through Art. 12: data-subject consent, a public-register transfer, contract necessity, vital-interest protection, legal obligation or court or prosecution order, and legal-claim preparation. This is a prohibition-with-listed-exceptions structure, the strictest transfer posture across this batch.
Section Five (Arts. 17-23) sets Bahrain's data-subject rights, each with its own working-day deadline. The Data Controller must notify a Data Subject who requests confirmation of processing within 15 working days (Art. 18(1)). It must halt or decline to begin direct-marketing processing and notify the Data Subject of its decision within 10 working days of a marketing objection (Art. 20(1)-(2)).
It must halt or decline to begin processing that causes material or moral damage within 10 working days of an objection on that ground (Art. 21(1)). It must respond to a rectification, blocking, or erasure request within 10 working days (Art. 23(1)).
Art. 17 separately requires the Data Controller to brief the Data Subject on the purposes of processing at the time data is obtained, Art. 19 requires notice of the right to object to direct marketing, and Art. 22 gives a Data Subject a right against a decision based solely on automated processing. Art. 32 (Conflict of Interest) governs PDPA Board members and has no bearing on data-subject rights; the deadlines above rest on the Section Five articles that carry them.
The Personal Data Protection Authority (PDPA), established by Art. 27, enforces the Law.
Penalties are dual-track: under Art. 58, imprisonment up to one year and/or a fine of BD 1,000 to BD 20,000 for a list of violations including unlawful sensitive-data processing (Art. 5), unlawful cross-border transfer (Arts. 12-13), failure to notify the Authority of processing (Art. 14), processing without Art. 15 prior authorisation, and providing false information or obstructing inspectors; Art. 58(2)'s separate BD 3,000 to BD 20,000 fine is for a PDPA Board member's or employee's own breach of the Art. 32 conflict-of-interest duty, not a Data Controller's data-handling violation.
Art. 59 doubles these fines for a legal person committing the offense in its name or for its benefit. Art. 55 supplies a separate administrative track: a daily compliance penalty (BD 1,000 per day on a first violation, BD 2,000 per day on a repeat violation within three years) and an administrative penalty up to BD 20,000, plus withdrawal of an Art. 15 authorisation.
Art. 57 gives a Data Subject a private right of action: a party who suffers damage from a Data Controller's or Data Protection Guardian's processing of their personal data, or from a Data Protection Guardian's violation of the Law, is entitled to claim compensation from the Data Controller or Data Protection Guardian, without prejudice to the Civil Law.
Art. 1's Sensitive Personal Data definition covers race, ethnical origin, political or philosophical opinions, religious beliefs, union affiliation, criminal record, and health or sexual status. Biometric data is absent from this list, the same gap found in Qatar's PDPPL; it is instead regulated separately under Art. 15 (see the biometric privacy instrument).
Art. 5(3) exempts data the Data Subject has made publicly available from the Sensitive Personal Data consent rule, but because biometric data is not itself Sensitive Personal Data, this exemption does not textually reach Art. 15's separate biometric prior-authorisation gate.
Bahrain has no scraping-specific statute, so general law governs each dimension separately.
The Copyright Law (Law No. 22 of 2006 on the Protection of Copyright and Neighbouring Rights, as amended) excludes bare news of current events from protection outright, and separately permits, without the author's permission, reproducing a brief section of a legally published work to quote it in another work for a legitimate purpose and to the extent necessary for that purpose, with the source and author's name mentioned where indicated in the source; nothing caps that exception at a short-extract length distinct from the necessity test.
The same Law extends protection to a collection of works or data, including a database in computer-readable or other form, as a derivative work where its selection or arrangement is creative, which is a compilation copyright rather than a separate sui generis database right, and infringing any protected right carries imprisonment of three months to one year and a fine of BD 500 to BD 4,000 or either penalty.
Bahrain's Personal Data Protection Law, researched separately under this jurisdiction's privacy record, applies to personal data with no general carve-out for information the data subject has made public, so scraping personal data from a public Bahraini page remains subject to that Law's lawful-basis and cross-border-transfer duties.
No Bahraini court has ruled on the enforceability of a browsewrap or clickwrap terms-of-service against a scraper, and no statute or reported case establishes a scraping-specific unfair-competition, misappropriation, or trespass doctrine, or assigns legal weight to a robots.txt directive or imposes an AI-training-specific rule.
Article 21(1) permits, without the author's permission and without payment of compensation, reproducing a brief section of a legally published work to quote it in another work, provided the quotation serves a legitimate purpose and does not exceed the extent necessary for that purpose, with the source and author's name mentioned where indicated in the source.
Anyone who infringes a right protected under the Law, including by exceeding this exception's necessary extent, is subject to imprisonment of three months to one year and a fine of BD 500 to BD 4,000, or either penalty. Article 81 provides that the Law takes effect from the day following the date of its publication in the Official Gazette. No source located states the resulting day.
Article 3(2) protects, as a derivative work, a collection such as an encyclopedia or a database in a computer-readable or other format, whether the collection is created through the selection or arrangement of its contents, without prejudice to protection of the original works the collection draws on.
Article 4 separately excludes abstract ideas, data, statutes, court judgments, and bare news of current events from protection, but its closing sentence extends protection to a collection of that excluded material where the compilation is itself creative in its selection or arrangement.
Because data itself is on that Article 4 exclusion list, extracting the underlying facts or data from a compiled database falls outside this protection even where the compilation's own selection or arrangement is protected. Article 81 provides that the Law takes effect from the day following the date of its publication in the Official Gazette. No source located states the resulting day.
Bahrain has no standalone statute setting security requirements a software product or connected device must meet before or after it reaches the market, and no general reasonable-security or information-security-programme statute binding a business with no sector gate.
The Personal Data Protection Law (Law No. 30 of 2018) carries its own security-of-processing article, Article 8, requiring a data controller to implement appropriate technical and organizational measures against accidental or unauthorized destruction, loss, alteration, disclosure or access, taking into account the state of the art, cost, the nature of the data and the risks involved; that clause is documented as this jurisdiction's privacy-topic instrument (comprehensive regime and lawful basis) rather than repeated here, the way a comprehensive data-protection act's own safeguards article sits in privacy rather than security.
Law No. 60 of 2014 on Combating Information Technology Crimes punishes unauthorized access to and interference with a computer system, an offence committed against a system rather than a duty on its operator or manufacturer, and stays with the scraping topic. The Central Bank of Bahrain's Rulebook Volume 1 (conventional banks), Module OM (Operational Risk Management), Section OM-5.5, Cyber Security Risk Management, is a binding sectoral regime added .
It assigns the board and senior management named cyber-security governance duties, and requires a cyber-security strategy and policy, prevention controls, risk identification and assessment, incident detection and recovery, cyber-security insurance, and staff training.
Rule OM-5.5.57, last amended April 2022, requires a conventional bank licensee that detects a cyber security incident, internal or external, that compromises customer information or disrupts a critical service, to contact the Central Bank by telephone within one hour and submit a Cyber Security Incident Report within two hours. A circular forwards National Cyber Security Centre guidance, titled Protect Your Organization, to banks.
Its cyber security risk-management module and the incident-reporting rules of the Central Bank's Rulebook volumes for conventional banks, Islamic banks, insurance, investment business and crypto-asset licensees are filed as rows of their own. A compliance-vendor summary of Bahraini law names a Bahrain Cybersecurity Law (Law No. 16 of 2018) and a Critical National Infrastructure Protection Law (Law No. 15 of 2018).
Bahrain's official legislative portal publishes Law No. 16 of 2018 as Bahrain's ratification of a privileges-and-immunities agreement with the Organisation for the Prohibition of Chemical Weapons, and Law No. 15 of 2018 as an amendment to the Societies and Clubs Law; neither concerns cybersecurity or critical infrastructure, so neither citation is treated as an instrument here.
Bahrain's National Cyber Security Centre publishes a National Cybersecurity Strategy for 2025 to 2028 and voluntary resources, a guide for micro, small and medium enterprises, public awareness campaigns and a self-assessment tool, rather than administering a statute; no legal instrument establishing a private-sector duty to report an incident to it is identified, so its role reads as coordination and awareness rather than a security-topic finding.
The Telecommunications Regulatory Authority's own site names Legislative Decree No. 48 of 2002 (the Telecommunications Law) as its governing instrument; its regulations index loads through a keyword search rather than a browsable list, so whether it maintains a standalone cybersecurity directive for a licensed telecom operator is not established here. Rule OM-5.5.22 requires conventional bank licensees to conduct periodic assessments of cyber threats.
Rule OM-5.5.57 requires conventional bank licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour.
Rule OM-5.5.57 requires Islamic bank licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour.
Rule RM-9.1.58 requires licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour.
Rule Cyber Resilience Act (CRA)-5.8.33 requires licensees that detect a cyber security incident, whether internal or external, that compromises client information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour. Rule RM-9.1.1 requires the Board of insurance licensees to ensure that the licensee has a robust cyber security risk management framework to manage its cyber security risk and vulnerabilities.
Conventional Banks Cyber Security Risk Management Rules Central Bank of Bahrain Rulebook Volume 1, Module OM, paragraphs OM-5.5.22 to OM-5.5.56Central Bank of Bahrain Rulebook, Volume 1 (Conventional Banks), published by the Central Bank of Bahrain
In force.Binds private bodies.
What this law does
Rule OM-5.5.22 requires conventional bank licensees to conduct periodic assessments of cyber threats. Rule OM-5.5.25 requires conventional bank licensees to conduct regular technical assessments to identify potential security vulnerabilities for systems, applications and network devices.
Rule OM-5.5.31 requires conventional bank licensees to implement cyber security incident management processes for timely detection, response and recovery, including a Security Information and Event Management system. Rule OM-5.5.35 requires conventional bank licensees to establish a Security Operations Centre. Rule OM-5.5.45 requires conventional bank licensees to identify the critical systems and services that must be recovered on a priority basis.
Rule OM-5.5.53 requires conventional bank licensees to arrange to seek cyber risk insurance cover from a suitable insurer. Rule OM-5.5.55 requires the licensee to ensure that all employees receive adequate training on a regular basis in relation to cyber security and the threats they could encounter. No commencement notice for the provisions this entry describes has been located.
Rule RM-9.1.1 requires the Board of insurance licensees to ensure that the licensee has a robust cyber security risk management framework to manage its cyber security risk and vulnerabilities. Rule RM-9.1.3 requires the cyber security risk management framework to be developed in accordance with the National Institute of Standards and Technology (NIST) Cyber security framework. Rule RM-9.1.32 requires licensees to implement cyber security incident management processes for timely detection, response and recovery.
Rule RM-9.1.46 requires licensees to identify the critical systems and services that must be recovered on a priority basis. Rule RM-9.1.54 requires licensees to arrange to seek cyber risk insurance cover from a suitable insurer. Rule RM-9.1.56 requires the licensee to ensure that all employees receive adequate training on a regular basis in relation to cyber security and the threats they could encounter. No commencement notice for the provisions this entry describes has been located.
Conventional Banks Cyber Security Incident Reporting Rules Central Bank of Bahrain Rulebook Volume 1, Module OM, paragraphs OM-5.5.57 to OM-5.5.59Central Bank of Bahrain Rulebook, Volume 1 (Conventional Banks), published by the Central Bank of Bahrain
In force.Binds private bodies.
What this law does
Rule OM-5.5.57 requires conventional bank licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour. Rule OM-5.5.57 requires the licensee to submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours.
Rule OM-5.5.58 requires the licensee to submit Section B of the Cyber Security Incident Report within 10 calendar days of the occurrence of the incident. Rule OM-5.5.58 requires a weekly progress update to the Central Bank of Bahrain until the incident is fully resolved. Rule OM-5.5.59 says the licensee should submit the report with as much information as possible even if all the details have not been obtained yet. No commencement notice for the provisions this entry describes has been located.
Crypto-Asset Cyber Security Incident Reporting Rules Central Bank of Bahrain Rulebook Volume 6, Module CRA, paragraphs CRA-5.8.33 to CRA-5.8.35Central Bank of Bahrain Rulebook, Volume 6 (Capital Markets), published by the Central Bank of Bahrain
In force.Binds private bodies.
What this law does
Rule Cyber Resilience Act (CRA)-5.8.33 requires licensees that detect a cyber security incident, whether internal or external, that compromises client information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour. Rule CRA-5.8.33 requires the licensee to submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours.
Rule CRA-5.8.34 requires the licensee to submit Section B of the Cyber Security Incident Report within 10 calendar days of the occurrence of the incident. Rule CRA-5.8.34 requires a weekly progress update to the Central Bank of Bahrain until the incident is fully resolved. Rule CRA-5.8.35 says the licensee should submit the report with as much information as possible even if all the details have not been obtained yet. No commencement notice for the provisions this entry describes has been located.
Rule RM-9.1.58 requires licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour. Rule RM-9.1.58 requires the licensee to submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours.
Rule RM-9.1.59 requires the licensee to submit Section B of the Cyber Security Incident Report within 10 calendar days of the occurrence of the incident. Rule RM-9.1.59 requires a weekly progress update to the Central Bank of Bahrain until the incident is fully resolved. Rule RM-9.1.60 says the licensee should submit the report with as much information as possible even if all the details have not been obtained yet. No commencement notice for the provisions this entry describes has been located.
Investment Business Cyber Security Incident Reporting Rules Central Bank of Bahrain Rulebook Volume 4, Module RM, paragraphs RM-9.1.58 to RM-9.1.60Central Bank of Bahrain Rulebook, Volume 4 (Investment Business), published by the Central Bank of Bahrain
In force.Binds private bodies.
What this law does
Rule RM-9.1.58 requires licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour. Rule RM-9.1.58 requires the licensee to submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours.
Rule RM-9.1.59 requires the licensee to submit Section B of the Cyber Security Incident Report within 10 calendar days of the occurrence of the incident. Rule RM-9.1.59 requires a weekly progress update to the Central Bank of Bahrain until the incident is fully resolved. Rule RM-9.1.60 says the licensee should submit the report with as much information as possible even if all the details have not been obtained yet. No commencement notice for the provisions this entry describes has been located.
Islamic Banks Cyber Security Incident Reporting Rules Central Bank of Bahrain Rulebook Volume 2, Module OM, paragraphs OM-5.5.57 to OM-5.5.59Central Bank of Bahrain Rulebook, Volume 2 (Islamic Banks), published by the Central Bank of Bahrain
In force.Binds private bodies.
What this law does
Rule OM-5.5.57 requires Islamic bank licensees that detect a cyber security incident, whether internal or external, that compromises customer information or disrupts critical services that affect operations to contact the Central Bank of Bahrain immediately, within one hour. Rule OM-5.5.57 requires the licensee to submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours.
Rule OM-5.5.58 requires the licensee to submit Section B of the Cyber Security Incident Report within 10 calendar days of the occurrence of the incident. Rule OM-5.5.58 requires a weekly progress update to the Central Bank of Bahrain until the incident is fully resolved. Rule OM-5.5.59 says the licensee should submit the report with as much information as possible even if all the details have not been obtained yet. No commencement notice for the provisions this entry describes has been located.
Bahrain has no press-publisher neighbouring right and no mandatory platform-to-publisher bargaining code; the general copyright framework of the Copyright Law (Law No. 22 of 2006 on the Protection of Copyright and Neighbouring Rights, as amended) is the only law reaching an aggregator's reproduction of news content.
Article 4(3) excludes news of current events that may merely be news reports from copyright protection outright, so a bare fact or news item is never protectable regardless of who first reported it, though the same Article's closing sentence protects a collection of such items where the compilation is itself creative in its selection or arrangement.
Article 21(1) separately permits, without the author's permission, reproducing a brief section of a legally published work to quote it in another work for a legitimate purpose and to the extent that purpose requires, with the source and author's name mentioned where indicated in the source; nothing limits that exception to a short-extract or headline-length threshold, and no reported Bahraini decision applies it to a systematic news aggregator as opposed to an individual quotation.
Neighbouring rights under the Law protect performing artists and broadcasting organizations, not a print or online news publisher's own reporting.
No statute or case law addresses whether a hyperlink is itself a communication to the public, or whether framing or inline display changes the answer, no hot-news or misappropriation doctrine distinct from ordinary copyright law exists, and the Law predates the concept of a machine-readable text-and-data-mining reservation, so no opt-out mechanism of that kind exists either.
Article 4(3) excludes news of current events that may merely be news reports from copyright protection, so a bare fact or news item is never a protected work in Bahrain, whichever outlet reports it first; the Article's closing sentence nonetheless protects a collection of such items where the compilation is itself creative in its selection or arrangement.
Article 21(1) separately permits, without the author's permission and without payment of compensation, reproducing a brief section of a legally published work to quote it in another work, provided the quotation serves a legitimate purpose and does not exceed the extent that purpose requires, with the source and author's name mentioned where the source indicates them.
Neighbouring rights under the Law, covering performing artists and broadcasting organizations, do not extend to a print or online news publisher's own reporting. Article 81 provides that the Law takes effect from the day following the date of its publication in the Official Gazette. No source located states the resulting day.
These areas of law were researched here and no instrument was recorded. Each finding says what the research checked, as of the date under it. It describes our search, not a guarantee that no such law exists.
AI law
Bahrain has no enacted statute specific to AI transparency or output labelling, high-risk AI system obligations, AI training-data duties, prohibited AI practices, AI governance duties, or AI sector rules as of this review.
The Information and eGovernment Authority's General Policy for the Use of Artificial Intelligence (Version 1.0, ) sets transparency, human-oversight, and appeal expectations for government agencies deploying AI in public services and endorses the Gulf Cooperation Council's non-binding 2023 Guiding Manual on the Ethics of Artificial Intelligence Use, but by its own terms it binds government agencies rather than a private-sector app.
Bahrain's Personal Data Protection Law gives a data subject a right against a decision based solely on automated processing, researched under this jurisdiction's privacy record rather than here, because that duty attaches to personal data rather than to an AI system as such.
Press reporting describes the Shura Council, the appointed upper chamber of the National Assembly, as having approved a proposal in April 2024 recommending that the government prepare standalone artificial-intelligence legislation, with the government instead pointing to existing laws and a proposed regulatory sandbox, and reporting into 2026 describing the proposal as still under legislative review with no bill enacted or referred to the elected Council of Representatives.
As of .
Age gating law
Bahrain has no adult-content age-verification law, social-media minor-access restriction, app-store age-verification requirement, or age-appropriate design code.
The Child Law (Law No. 37 of 2012) defines a child as a person who does not exceed eighteen Gregorian years and criminalizes luring a child and exploiting the child via the internet or other modern means of communication in matters contrary to public morals and public order or inappropriate to the child's age (Arts. 57, 66), and separately criminalizes sexually harassing a child with foreplay, showing nudity, or coercing the child into watching pornographic images or movies in any way including the internet (Art. 67), but neither provision imposes an age-verification or age-gating duty on a service provider.
As of .
Case law
No current case law for Bahrain AI law
No current case law for Bahrain privacy law
No current case law for Bahrain scraping law
No current case law for Bahrain cybersecurity law
No current case law for Bahrain communications law
No current case law for Bahrain content moderation law
No current case law for Bahrain product and AI liability law
No current case law for Bahrain digital accessibility law
No current case law for Bahrain age gating law
No current case law for Bahrain reuse law
Reporting clocks that run here5 instruments
The instruments whose obligation lines set a deadline for reporting an incident, a vulnerability or a personal-data breach, each deadline read from the sentence that carries it and listed shortest first. The law of Bahrain comes first, then the law of the bodies above it that applies here.
Each flag is one law, and a link to it. Read down the scale: the clocks document's time axis, with the empty stretches shortened so the deadlines sit close. Flags on one line set the same duty at the same deadline, and the laws behind them are named to the right, with what each clock counts from.
The deadlines above on one time axis, shortest at the top. The axis keeps its order and, between neighbors, its proportion, but a stretch with no deadline on it is shortened, so the hour marks on the left are what say how far apart two stations really are. Beside each action, the laws that set it, what each counts from, and a status where the law is not yet in force. The List tab has the same data in full, with the sentences.
Submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours (OM-5.5.57).
Submit Section B of the Cyber Security Incident Report within 10 calendar days of the incident, with the full root cause analysis, the impact on business operations and customers, and the measures taken to stop the attack and prevent a recurrence, and send a weekly progress update until the incident is fully resolved (OM-5.5.58).
Submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours (Cyber Resilience Act (CRA)-5.8.33).
Submit Section B of the Cyber Security Incident Report within 10 calendar days of the incident, with the full root cause analysis, the impact on business operations and clients, and the measures taken to stop the attack and prevent a recurrence, and send a weekly progress update until the incident is fully resolved (Cyber Resilience Act (CRA)-5.8.34).
Submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours (RM-9.1.58).
Submit Section B of the Cyber Security Incident Report within 10 calendar days of the incident, with the full root cause analysis, the impact on business operations and customers, and the measures taken to stop the attack and prevent a recurrence, and send a weekly progress update until the incident is fully resolved (RM-9.1.59).
Submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours (RM-9.1.58).
Submit Section B of the Cyber Security Incident Report within 10 calendar days of the incident, with the full root cause analysis, the impact on business operations and customers, and the measures taken to stop the attack and prevent a recurrence, and send a weekly progress update until the incident is fully resolved (RM-9.1.59).
Submit Section A of the Cyber Security Incident Report to the Central Bank of Bahrain's cyber incident reporting email within two hours (OM-5.5.57).
Submit Section B of the Cyber Security Incident Report within 10 calendar days of the incident, with the full root cause analysis, the impact on business operations and customers, and the measures taken to stop the attack and prevent a recurrence, and send a weekly progress update until the incident is fully resolved (OM-5.5.58).
Which of these one incident starts turns on the facts: the incident method works that through. The clocks document draws every clock in the LexLint law library on one axis, with the sentence beside every rung.
AIDrafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
This page covers the instruments LexLint has researched
to a stage. Instruments named in the law library but not yet researched are
counted in the head and are not listed here. Every entry carries its own
primary source on its note page. This is a research index, not legal
advice.