United States law applies in West VirginiaWest Virginia is a state of the United States, whose 134 researched instruments are listed on the United States page, not here. The law of West Virginia, described on this page below, applies here too.
7 of 9 named instruments researched to a stage, across five of the ten areas of law we track: 7 in force. As of .
When each starts5 of 7 carry a date, 2 do not.
in forcenot yet in forceblocked by a courtproposedno longer in force
West Virginia enacted Senate Bill 198 in 2025, in effect since , which amended the state's child sexual abuse material statute to reach a visual portrayal created or altered by artificial intelligence that is indistinguishable from a real minor or that depicts an identifiable minor, and separately amended the state's nonconsensual intimate image statute to reach a fabricated intimate image, one created by artificial intelligence or other computer technology, disclosed or threatened to be disclosed with intent to harass, intimidate, threaten, humiliate, embarrass, or coerce.
Both are criminal prohibitions binding any person; neither is a consumer-facing transparency or labeling duty.
West Virginia has not enacted a general AI-content disclosure statute or an election-deepfake disclosure law: House Bill 4496 (2026), which would have required a disclosure marker on AI-created or AI-altered media generally, was introduced, referred to House Judiciary on , and never advanced before the session ended; Senate Bill 484 (2025), which would have added a new election code section requiring disclosure of synthetic media and artificial intelligence used to influence an election, was referred to Rules on first reading on and never advanced.
West Virginia has created a West Virginia Task Force on Artificial Intelligence within the Office of the Governor (W. Va. Code § 5A-6-9, enacted 2024 by H.B. 5690 and its mandate extended by H.B. 3187 in 2025), an advisory and institutional body that studies AI's effects on the workforce and government use and recommends legislation; it imposes no direct requirement on a commercial entity or automated system and is not catalogued as an instrument here.
Senate Bill 198 (2025) amended West Virginia's Filming of Sexually Explicit Conduct of Minors article to define computer-generated child pornography as a visual portrayal of an identifiable minor that has been created, adapted, or modified to depict the minor engaged in sexually explicit conduct, or a visual portrayal that appears to depict a minor engaged in sexually explicit conduct where the portrayal was created by artificial intelligence or other computer technology and is indistinguishable from a minor.
Any person who knowingly sends, distributes, exhibits, possesses, electronically accesses with intent to view, displays, or transports such material, alongside traditional child pornography, is guilty of a felony, with three graduated sentencing tiers keyed to the number of images involved. The prohibition binds any person and does not depend on whether the depicted minor's actual identity can be ascertained.
W. Va. Code § 61-8-28aofficial West Virginia Code text, West Virginia Legislature website (code.wvlegislature.gov)
In force since .Binds public and private bodies.
What this law does
Senate Bill 198 (2025) amended West Virginia's nonconsensual disclosure of private intimate images statute to add a fabricated intimate image, an image of an identifiable person that was created using artificial intelligence or other computer technology and depicts computer-generated intimate parts, or the intimate parts of another person, as that individual's own.
No person may knowingly and intentionally disclose, cause to be disclosed, or threaten to disclose a fabricated intimate image, or a genuine intimate image captured with a reasonable expectation of privacy, with intent to harass, intimidate, threaten, humiliate, embarrass, or coerce. A first violation is a misdemeanor; a second or subsequent violation is a felony.
The statute exempts images disclosed with prior written consent, images of voluntary public or commercial exposure, and disclosures made through lawful reporting, legal proceedings, or medical treatment, and it does not impose liability on an interactive computer service, information service, or telecommunications service provider for content supplied by another person.
West Virginia has no enacted comprehensive personal-data statute.
Its only enacted personal-data statute of general application is the Breach of Security of Consumer Information Act, W. Va. Code secs. 46A-2A-101 to 46A-2A-105, in force since the 2008 Regular Session; it does not fold biometric, genetic, or health data into personal information at all, and its notice-violation deeming clause is closed to a private plaintiff by the statute's own exclusivity language, overriding what would otherwise be an open path through West Virginia's general unfair-trade-practices private action.
An individual or entity that owns or licenses computerized data including personal information must give notice of a breach of the security of the system, without unreasonable delay, to any West Virginia resident whose unencrypted and unredacted personal information was or is reasonably believed to have been accessed and acquired by an unauthorized person, where the breach causes or is reasonably believed to cause identity theft or other fraud.
The Act's definition of entity includes governments, governmental subdivisions, agencies and instrumentalities, so the duty binds a public body as well as a private one. Personal information is name plus a Social Security number, driver's license or state ID number, or a financial account number with access credential; health information, biometric data, and genetic data are not folded into this definition, unlike South Dakota's narrower biometric fold-in researched alongside this state.
An entity required to notify more than 1,000 persons of a breach must also notify nationwide consumer reporting agencies.
A notice violation is deemed an unfair or deceptive act under West Virginia's general Consumer Credit and Protection Act, but the Attorney General has exclusive authority to bring that action (except against a licensed financial institution, enforced instead by its own primary regulator), which closes the private right of action that West Virginia's general unfair-trade-practices statute, W. Va. Code sec. 46A-6-106, would otherwise open for 'any person who purchases or leases goods or services' suffering an ascertainable loss.
The Act that enacted these sections, Senate Bill 340 of the 2008 Regular Session, was passed on and states that it is in effect ninety days from passage. No source stating the resulting day has been located.
West Virginia's computer-misuse statute, the West Virginia Computer Crime and Abuse Act, criminalizes access to a computer or computer network only when it is done knowingly and willfully, and either without authorization (for the misdemeanor of obtaining computer services) or with fraudulent intent (for the felony of computer fraud); ordinary, non-deceptive automated reading of a public page fits neither offense's elements on its face, and no reported West Virginia case applies either section to scraping or automated collection.
Unlike Virginia's neighboring statute, West Virginia's Act contains no express savings clause preserving contract or license terms, so terms-of-service enforceability against a scraper rests on ordinary West Virginia contract law with no statutory guidance either way, and no West Virginia case addresses browsewrap or clickwrap enforceability for a scraping dispute.
West Virginia has no comprehensive consumer-data-protection statute: House Bill 2987 passed the House in 2025 but died in Senate committee, so scraped public personal data is reached only by the Breach of Security of Consumer Information Act, which regulates notice after a breach and imposes no duty on the act of collecting or scraping personal data at all.
Copyright, text-and-data-mining, and database rights are federal only; West Virginia adds nothing there, and no West Virginia statute or case gives robots.txt independent legal weight.
Section 61-3C-5 makes it a misdemeanor, fined $200 to $1,000 or up to one year in county jail, for any person to knowingly, willfully, and without authorization access or cause to be accessed a computer or computer network with the intent to obtain computer services; ordinary, non-deceptive automated access to a public page performed without such intent does not fit this offense's elements.
Section 61-3C-4 separately makes computer fraud, accessing a computer to execute a scheme to defraud or to obtain money, property, or services by fraudulent pretenses, a felony punishable by up to $10,000 and ten years, and makes introducing ransomware with intent to extort a separate felony punishable by up to $100,000 and ten years; a third tier in the same section punishes knowing, willful, unauthorized access to data stored in a computer owned by the Legislature with a fine of up to $5,000 and up to five years.
Authorization is defined as the express or implied consent a person gives another to access their computer, network, program, software, system, password, identifying code, or personal identification number.
Section 61-3C-17 provides a defense where the defendant had reasonable grounds to believe they had authority to access, or could not reasonably have known they lacked it, but the article contains no clause preserving or displacing ordinary contract or license terms, unlike Virginia's equivalent statute.
Section 61-3C-16 gives any person injured by a violation of the article a civil cause of action in circuit court for compensatory damages, punitive damages, and injunctive relief, brought within five years of the last act constituting a violation or two years of its discovery, whichever is earlier. The Act was originally enacted in 1989 as Senate Bill 92 and has been amended repeatedly since. The provisions this entry describes came into force on different days.
West Virginia has no enacted statute imposing a general reasonable-security-procedures, information-security-program, or records-disposal duty on a private-sector business that is distinct from breach notification, no enacted product-security or connected-device statute, no enacted statute adopting the National Association of Insurance Commissioners' Insurance Data Security Model Law, and no enacted sector cyber-resilience regime a LexLint activity can express.
West Virginia's only enacted computer-security statute of general application, W. Va. Code secs. 46A-2A-101 to 46A-2A-105, sits entirely within an article titled Breach of Security of Consumer Information: its five sections cover definitions (46A-2A-101), notice of a breach of security of computerized personal information (46A-2A-102), procedures deemed in compliance with the notice requirement (46A-2A-103), violations (46A-2A-104), and applicability (46A-2A-105), and impose no separate duty to safeguard, encrypt, or dispose of personal information before a breach occurs; that breach-notification duty is already this jurisdiction's privacy-topic row and is not repeated here.
The full article list of Chapter 46A, the West Virginia Consumer Credit and Protection Act, carries no article addressing records disposal, a written information-security program, or reasonable safeguards: its consumer-protection articles run from General Consumer Protection (Article 6) through the Storm Scammer Consumer Protection Act and Consumer Litigation Financing (Articles 6M and 6N), with no disposal or safeguards article comparable to Georgia's, Arizona's, Alaska's, or Hawaii's, and its Article 6L, captioned Theft of Consumer Identity Protections, is a consumer credit-report security-freeze statute rather than a security-posture duty on a business.
The West Virginia Insurance Code, Chapter 33, likewise carries no article addressing an insurer's or insurance licensee's information-security program or a cybersecurity event: the chapter's full article list, from Article 1 through Article 64, includes only the older National Association of Insurance Commissioners privacy model at Article 6F (Disclosure of Nonpublic Personal Information), a privacy-topic matter, and no analog to the newer NAIC Insurance Data Security Model Law already adopted in South Carolina, Hawaii, Alaska, Arizona, and Wisconsin.
The nearest thing West Virginia has to a private-sector security-baseline statute did not become law.
House Bill 2987 (2025 Regular Session), an Engrossed Committee Substitute reported from the House Energy and Public Works Committee on and titled in part Safe Harbor for Cybersecurity Programs and the Consumer Data Protection Act, would have added a new Chapter 31A, Article 8H (Safe Harbor for Cybersecurity Programs, secs. 31A-8H-1 to 31A-8H-5) giving a covered entity an affirmative defense against exemplary or punitive damages in a data-breach lawsuit where it created, maintained, and complied with a written cybersecurity program reasonably conforming to a named industry framework (the National Institute of Standards and Technology (NIST) framework for improving critical infrastructure cybersecurity, NIST SP 800-171, NIST SP 800-53 and 800-53A, NIST SP 800-76-1, the FedRAMP Security Assessment Framework, the CIS Critical Security Controls, the ISO/IEC 27000 family, or CMMC Level 2 with external certification, or a sector regime such as the Health Insurance Portability and Accountability Act (HIPAA) Security Rule or Gramm-Leach-Bliley Title V), alongside a new Chapter 46A, Article 6O Consumer Data Protection Act.
The bill passed the House on (Roll No. 194) with a House-set effective date of (Roll No. 195), was communicated to the Senate, and was referred to the Senate Judiciary Committee on ; the West Virginia Legislature's own bill-status record shows no further action after that referral, and no companion or successor enactment reaching Chapter 31A or Chapter 46A, Article 6O, is confirmed.
Neither article appears in the current, live article list of Chapter 31A (Banks and Banking, running through Article 8G and Article 9, the Uniform Special Deposits Act) or of Chapter 46A read here, and because , the bill's own stated effective date, has already passed without either new article appearing in the code, the absence reflects the bill's death in Senate committee rather than a codification lag.
West Virginia's Cyber Security Program, W. Va. Code secs. 5A-6B-1 to 5A-6B-6, within the Department of Administration's Office of Technology, and its West Virginia Cyber Incident Reporting article, secs. 5A-6C-1 to 5A-6C-4, are both government-only regimes.
The Cyber Security Program's own scope section states that its provisions are 'applicable to all state agencies, excluding higher education institutions, the State Police, state constitutional officers identified in section 6-7-2 of this code, the Legislature, and the Judiciary,' and the Cyber Incident Reporting article's own scope section states that it 'applies to all state agencies within the executive branch, constitutional officers, all local government entities as defined by section 7-1-1 or section 8-1-2 of this code, county boards of education as defined by section 18-1-1 of this code, the Judiciary, and the Legislature.'
Neither section extends either duty to a vendor or contractor doing business with the state; both are filed as rows of their own with no activity flag. No enacted West Virginia statute is confirmed in the primary text consulted here to set security requirements a connected device or software product must meet to be placed on the market, comparable to California's or Oregon's connected-device statutes or the Cyber Resilience Act.
West Virginia's Computer Crime and Abuse Act, W. Va. Code secs. 61-3C-1 et seq., penalizes a person who accesses a computer without authorization; that offense is committed against a system by an intruder rather than a duty on the system's operator or manufacturer, so it belongs to the scraping topic's computer-misuse family and is not filed here.
West Virginia Code section 5A-6C-3 requires qualified cybersecurity incidents to be reported to the Cybersecurity Office before any citizen notification, and no later than 10 days after a determination that the entity experienced a qualifying cybersecurity incident.
West Virginia Code section 5A-6B-4 requires each information custodian receiving centralized support from the West Virginia Office of Technology, or any other entity subject to the article, to undergo an appropriate cyber risk assessment.
The West Virginia Cybersecurity Office is created within the Office of Technology, to be led by the West Virginia Chief Information Security Officer, and may set standards for cybersecurity and is charged with managing the cybersecurity framework. The article applies to all state agencies, excluding higher education institutions, the State Police, state constitutional officers identified in section 6-7-2 of the code, the Legislature, and the Judiciary.
Each information custodian receiving centralized support from the West Virginia Office of Technology, or any other entity subject to the article, must undergo an appropriate cyber risk assessment as required by the cybersecurity framework or as directed by the Chief Information Security Officer.
The information custodian must adhere to the cybersecurity standard established by the Chief Information Security Officer in the use of information technology infrastructure and to enterprise cybersecurity policies and standards. The information custodian must participate in at least one annual cybersecurity program review with representatives of the West Virginia Office of Technology before November 30 of each year.
An information custodian is a state or local department, agency, office, board, commission, or other spending unit with custody of, or responsibility for, data assets residing on a state system, device, account, or networks owned, monitored, or maintained by the West Virginia Office of Technology.
If an information custodian fails to participate in the annual cybersecurity program review, the West Virginia Office of Technology may recover expenses associated with conducting any diagnostics or evaluations performed to assure safety of the network, devices, and systems. House Bill 5638 amended and reenacted sections 5A-6B-1 through 5A-6B-6 of the code. House Bill 5638 was passed and took effect 90 days from passage, on .
Qualified cybersecurity incidents must be reported to the Cybersecurity Office before any citizen notification, but no later than 10 days following a determination that the entity experienced a qualifying cybersecurity incident.
A qualified cybersecurity incident meets at least one of three criteria: state or federal law requires the reporting of the incident to regulatory or law-enforcement agencies or affected citizens, the ability of the entity to conduct business is substantially affected, or the incident would be classified as emergency, severe, or high by the federal Cybersecurity and Infrastructure Security Agency.
The report must contain at a minimum the approximate date of the incident, the date the incident was discovered, the nature of any data that may have been illegally obtained or accessed, and a list of the state and federal regulatory agencies, self-regulatory bodies, and foreign regulatory agencies to whom the notice has been or will be provided.
The article applies to all state agencies within the executive branch, constitutional officers, all local government entities, county boards of education, the Judiciary, and the Legislature. An incident is a violation, or imminent threat of violation, of computer security policies, acceptable use policies, or standard security practices. The Cybersecurity Office establishes the procedure for reporting cybersecurity incidents and disseminates it to the covered entities.
West Virginia enacted its first age-gating statute in 2026, a law creating civil liability for commercial entities that fail to verify the age of users accessing sexual material harmful to minors, effective . Earlier attempts in 2024 and 2025 to enact adult content age verification or an app store parental consent requirement died in committee.
West Virginia has not enacted a social media minor access law or an age appropriate design code, though bills on both topics have been introduced.
Requires a commercial entity that knowingly and intentionally publishes or distributes sexual material harmful to minors, to verify that a user is 18 or older using digital identification or a commercial or governmental age verification system. Exempts news gathering organizations, internet service providers, search engines, and cloud service providers.
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.
Reuse law
West Virginia has no enacted press-publisher neighbouring right, mandatory platform-to-publisher bargaining code, or other news-aggregation-specific statute. West Virginia Code Chapter 47 (Regulation of Trade) and Chapter 61 (Crimes and Their Punishment) contain no provision addressing snippet reproduction, hot-news misappropriation, linking or framing, or a text-and-data-mining opt-out; no bill on any of these subjects appears among the state's recently enacted or pending legislation.
Snippet reproduction, hot-news misappropriation, and linking and framing in West Virginia are governed by the federal baseline recorded in the national aggregation document (Copyright Act fair use and preemption, and the general federal common-law hot-news doctrine); no reported West Virginia state court decision recognizes or declines a state-law hot-news claim.
As of .
Case law
No current case law for West Virginia AI law
No current case law for West Virginia privacy law
No current case law for West Virginia scraping law
No current case law for West Virginia cybersecurity law
No current case law for West Virginia communications law
No current case law for West Virginia content moderation law
No current case law for West Virginia product and AI liability law
No current case law for West Virginia digital accessibility law
No current case law for West Virginia age gating law
No current case law for West Virginia reuse law
Reporting clocks that run here18 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 West Virginia 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.
Report a qualified cybersecurity incident to the Cybersecurity Office before any citizen notification, and no later than 10 days after determining that the entity experienced a qualifying cybersecurity incident.
Notify the NRC Headquarters Operations Center via the Emergency Notification System within one hour after discovery of a cyberattack that adversely impacted safety-related or important-to-safety functions, security functions, or emergency preparedness functions (including offsite communications), or that compromised support systems and equipment resulting in adverse impacts to those functions.
Also notify within one hour after discovery of a cyberattack that adversely impacted the safety, security, and emergency preparedness functions performed by digital assets described in 10 CFR 73.77(a)(1)(ii).
Notify the NRC Headquarters Operations Center within four hours after discovery of a cyberattack that could have caused such an adverse impact, after discovery of a suspected or actual cyberattack initiated by personnel with physical or electronic access to the systems in scope, or after notifying a local, State, or other Federal agency of an event related to your cyber security program that does not otherwise require notification.
Notify the NRC Headquarters Operations Center within eight hours after receipt or collection of information regarding observed behavior, activities, or statements that may indicate intelligence gathering or pre-operational planning related to a cyberattack against the systems in scope.
Use the site corrective action program to record vulnerabilities, weaknesses, failures and deficiencies in your cyber security program, and the notifications you make, within twenty-four hours of their discovery.
Once the final rule takes effect, report a covered cyber incident to the Agency not later than 72 hours after your organization reasonably believes that the covered cyber incident has occurred.
Once the final rule takes effect, report a ransom payment to the Agency not later than 24 hours after your organization makes the payment, even where the underlying ransomware attack is not itself a covered cyber incident.
Once the final rule takes effect, promptly submit an update to a previously submitted covered cyber incident report whenever substantial new or different information becomes available or a ransom payment is later made, continuing until your organization notifies the Agency that the incident has concluded and been fully mitigated and resolved, and preserve data relevant to the incident or payment under the procedures the final rule establishes.
Upon any responsible SCI personnel having a reasonable basis to conclude that an SCI event has occurred, begin appropriate corrective action and notify the Commission of the SCI event immediately.
Within 24 hours of that conclusion, submit a written notification to the Commission, made on a good faith, best efforts basis, that describes the SCI event and the systems affected and, to the extent available, your assessment of the market participants potentially affected, the potential impact on the market, and the steps you have taken, are taking or plan to take.
If the SCI event is resolved and the investigation closed within 30 calendar days, submit a final written notification within five business days after resolution. If not, submit an interim written notification within 30 calendar days after the event, and a final one within five business days after resolution and closure.
If your organization is a banking organization, notify your primary federal banking regulator, the OCC, the Federal Reserve Board, or the FDIC, whichever supervises it, about a notification incident, as soon as possible and no later than 36 hours after your organization determines that a notification incident has occurred.
A notification incident is the subset of computer-security incidents that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, your ability to serve customers, a business line, or an operation whose failure would threaten the financial stability of the United States, so a computer-security incident that falls short of that threshold does not by itself start this clock.
If your organization is a bank service provider, notify at least one bank-designated point of contact at each affected banking organization customer as soon as possible after your organization determines that it has experienced a computer-security incident that has materially disrupted or degraded, or is reasonably likely to materially disrupt or degrade, covered services provided to that banking organization for a period of four hours or more.
This duty carries a standard, as soon as possible, rather than a fixed number of hours to notify by, and that disruption threshold is what engages the duty rather than a period to notify within.
If you are a developer or provider of a frontier AI model, or an operator of critical infrastructure that uses an AI model to manage industrial control systems or other operational technologies, report any confirmed AI safety incident or AI security incident within 30 days of confirmation, and within 72 hours if the incident poses an imminent threat to national security, critical infrastructure or public safety.
If your organization is a federally insured credit union, notify the NCUA-designated point of contact of a reportable cyber incident by email, telephone, or another method the NCUA prescribes, so that the NCUA receives the notification as soon as possible and no later than 72 hours after your organization reasonably believes it has experienced a reportable cyber incident.
Where the reportable cyber incident is a disruption of business operations or unauthorized access to sensitive data facilitated through, or caused by, a compromise of a credit union service organization, cloud service provider, or other third-party data hosting provider, or by a supply chain compromise, the NCUA must receive the notification within 72 hours of your organization being notified by the third party if that is sooner.
Send the notice as soon as practicable, but not later than 30 days, after becoming aware that unauthorized access to or use of customer information has occurred or is reasonably likely to have occurred, delaying it only for the period the United States Attorney General specifies where the Attorney General determines that notice poses a substantial risk to national security or public safety (17 CFR 248.30(a)(4)(iii)).
Maintain written policies and procedures reasonably designed to require oversight, including through due diligence and monitoring, of service providers, including that a service provider notify you as soon as possible, and no later than 72 hours, after becoming aware of a breach in security resulting in unauthorized access to a customer information system it maintains (17 CFR 248.30(a)(5)(i)).
Rapidly report a cyber incident to the Department of Defense within 72 hours of discovering it, at the Department's DIBNet portal (dibnet.dod.mil), using a DoD-approved medium assurance certificate that you must obtain before you need to file a report.
Make those policies and procedures reasonably designed to ensure that each service provider takes appropriate measures to protect against unauthorized access to or use of customer information, and to notify you as soon as possible, but no later than 72 hours after becoming aware that a breach in security has occurred resulting in unauthorized access to a customer information system the service provider maintains.
If your organization is an Securities and Exchange Commission (SEC) reporting company, determine, without unreasonable delay after you discover a cybersecurity incident, whether the incident is material, and if it is, file a Form 8-K under Item 1.05 within four business days after you make that determination.
If the information called for in Item 1.05 is not determined or is unavailable when you file, state that in the filing and file an amendment to the Form 8-K within four business days after you determine it or it becomes available.
After you reasonably determine that a breach of your customers' CPNI has occurred, electronically notify the United States Secret Service and the Federal Bureau of Investigation through the central reporting facility as soon as practicable, and in no event later than seven business days (47 CFR 64.2011(b)).
Do not notify customers or disclose the breach where the relevant investigating agency directs you in writing not to, for an initial period of up to 30 days that the agency may extend (47 CFR 64.2011(b)(3)).
If you are a vendor of personal health records (an entity that offers or maintains an electronic record of health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual) or a PHR related entity, notify each affected individual who is a citizen or resident of the United States, in plain language and without unreasonable delay, no later than 60 calendar days after you discover a breach of security of unsecured PHR identifiable health information.
Notify prominent media outlets serving a State or jurisdiction, without unreasonable delay and in no case later than 60 calendar days after you discover the breach, when the unsecured PHR identifiable health information of 500 or more of its residents is, or is reasonably believed to have been, acquired during the breach.
If you are a third party service provider, notify the official designated in a written contract by the vendor of personal health records or PHR related entity you serve (or else a senior official of that vendor or entity), without unreasonable delay and in no case later than 60 calendar days after you discover the breach; identify each customer of that vendor or entity whose unsecured PHR identifiable health information has been, or is reasonably believed to have been, acquired during the breach; and obtain acknowledgment that the notice was received.
Notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information.
For a breach of unsecured protected health information involving more than 500 residents of a State or jurisdiction, notify prominent media outlets serving that State or jurisdiction without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.
If you are a business associate, notify the covered entity of a breach of unsecured protected health information without unreasonable delay and in no case later than 60 calendar days after discovery of the breach.
If your organization is a derivatives clearing organization, notify staff of the Division of Clearing and Risk promptly of any hardware or software malfunction, security incident, or targeted threat that materially impairs, or creates a significant likelihood of material impairment of, automated system operation, reliability, security, or capacity, and of any activation of your business continuity and disaster recovery plan.
If your organization is a designated contract market, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and significant systems malfunctions and activations of your business continuity-disaster recovery plan.
If your organization is a swap execution facility, notify Commission staff promptly of all cyber security incidents or targeted threats that actually or potentially jeopardize automated system operation, reliability, security, or capacity, as well as electronic trading halts and material system malfunctions and activations of your business continuity-disaster recovery plan.
Evidence of sabotage, subversive activity, or an actual or threatened cyber incident involving or endangering any vessel, harbor, port, or waterfront facility must be reported immediately to the Federal Bureau of Investigation, the Cybersecurity and Infrastructure Security Agency (for any cyber incident), and the Captain of the Port, or to their respective representatives.
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.