Compliance

Texas Grid Cybersecurity: What ERCOT and PUCT Rules Mean for Your Organization

Texas electric organizations in the ERCOT region answer to state cybersecurity rules from the Public Utility Commission of Texas (PUCT) and ERCOT, in addition to any NERC requirements.

The PUCT oversees ERCOT, and Texas RE handles NERC compliance in the ERCOT region. State rules add a cybersecurity monitor program; an Emergency Operations Plan with a cyber security annex and a yearly March 15 filing; ERCOT incident notice; and vendor attestations. ALCON DTS supports the IT and security side of these programs, working alongside your compliance team.

At a glance

  • Regulator: the Public Utility Commission of Texas (PUCT), which certifies and oversees ERCOT
  • Key rules: PURA 39.1516 and 16 TAC 25.367 (cybersecurity monitor), 16 TAC 25.53 (Emergency Operations Plans), ERCOT Nodal Protocols (incident notice)
  • Yearly filing: Emergency Operations Plan filing due to the PUCT by March 15 (full plan at least once every three years, an update or attestation in the years between), with a cyber security annex in the plan
  • PUCT penalties: up to $25,000 per violation, with each day counted as its own violation, and up to $1 million per violation for certain violations (PURA 15.023)
  • NERC in Texas: Texas RE is the NERC Regional Entity for the ERCOT region
  • Last reviewed: October 27, 2026
Who’s who

Who oversees cybersecurity for the Texas grid?

  • PUCT. Certifies and oversees ERCOT. Under PURA 39.151(d), ERCOT “is directly responsible and accountable to the commission,” and the PUCT approves ERCOT protocols before they take effect.
  • ERCOT. The independent system operator for the ERCOT power region. Market participants “shall observe all scheduling, operating, planning, reliability, and settlement policies, rules, guidelines, and procedures established by the independent system operator in ERCOT” (PURA 39.151(j)).
  • Texas RE. The NERC Regional Entity for the ERCOT region. It handles NERC compliance monitoring and enforcement, which is distinct from PUCT enforcement of state rules. See our NERC CIP guide.
Who it covers

Do these rules apply to you?

Summary from PURA, 16 TAC 25.367, 16 TAC 25.53 and the ERCOT Nodal Protocols.
Rule Who it applies to
Cybersecurity monitor program (16 TAC 25.367) Mandatory for transmission and distribution utilities, PURA 32.053 corporations, and munis or co-ops that own or operate ERCOT transmission at 60 kV or more. Utilities outside ERCOT may opt in.
Emergency Operations Plan (16 TAC 25.53) Electric utilities, transmission and distribution utilities, power generation companies, munis, co-ops, retail electric providers and ERCOT
ERCOT incident notice (Nodal Protocols) ERCOT Market Participants
Vendor attestations (PURA 39.360) ERCOT market participants
Requirements

What do you need to have in place?

Cybersecurity monitor program

Under PURA 39.1516, the PUCT and ERCOT contract with a cybersecurity monitor to “manage a comprehensive cybersecurity outreach program for monitored utilities,” meet regularly on emerging threats, “review self-assessments voluntarily disclosed by monitored utilities,” and “report to the commission on monitored utility cybersecurity preparedness.”

  • Each monitored utility must name one or more points of contact who can answer the cybersecurity monitor’s questions about its cyber and physical security activities (16 TAC 25.367(m)(3)).
  • The monitor can “request, but not to require, information,” and self-assessments are voluntary.
  • The statute “does not grant enforcement authority to the cybersecurity monitor.”
  • The rule also runs a broader cybersecurity coordination program, open to all electric utilities, munis and co-ops, with guidance on best practices, information sharing and supply chain topics such as “software integrity and authenticity,” vendor risk management and “vendor remote access” (16 TAC 25.367; PURA 31.052).

Emergency Operations Plan

  • File with the PUCT by March 15 every year. File the full plan and an executive summary at least once every three years. In the years between, file an update: a revised plan if you made a change that materially affects your emergency response, or an attestation if you did not.
  • Include a cyber security annex and a physical security incident annex.
  • Conduct or take part in at least one drill each calendar year, and notify PUCT staff at least 30 days before at least one drill.
  • Give status updates on request during a TDEM State Operations Center activation.

ERCOT incident notice

A Market Participant must notify ERCOT as soon as practicable after it determines there is a Cybersecurity Incident on its computer network or system that interfaces with an ERCOT network or system. ERCOT defines a Cybersecurity Incident as “a malicious or suspicious act that compromises or disrupts a computer network or system that could foreseeably jeopardize the reliability or integrity of the ERCOT System or ERCOT’s ability to perform the functions of an independent organization” under PURA. Agents that transact with ERCOT for a Market Participant must report their incidents to it, and it reports them to ERCOT. Each Market Participant must also name and keep current a Cybersecurity Contact for communications with ERCOT (Nodal Protocols Section 16.18).

A proposed revision, NPRR1334, would expand notice to vendor systems that interface with ERCOT and to incidents on a Market Participant’s or its vendor’s systems that “could foreseeably jeopardize” the Market Participant’s own reliable operation. It is proposed, not adopted, and was tabled at ERCOT’s Protocol Revision Subcommittee on June 10, 2026.

Vendor attestations (Lone Star Infrastructure Protection Act)

ERCOT market participants must attest to compliance with Bus. and Com. Code Ch. 117. They must report purchases of critical electric grid equipment or services from listed foreign-adversary-linked companies and attest that the purchase will not give those companies access or control (PURA 39.360).

Is your cyber security annex ready for March 15? We will help you organize the IT portions of your annex and the evidence behind them.

Talk with ALCON DTS

Enforcement

How are the rules enforced?

  • General PUCT penalty. Up to $25,000 per violation, and each day a violation continues or occurs counts as its own violation (PURA 15.023(b)).
  • Higher caps. Up to $1,000,000 per violation, counted for each day, for violations of a voluntary mitigation plan or of the weatherization sections, PURA 35.0021 or 38.075 (15.023(b-1)). Up to $1 million for each violation when a market participant fails to submit required PURA 39.360 reports or attestations to ERCOT, or knowingly submits false information (15.023(b-2), added by SB 2368 in 2025).
  • NERC matters. Handled by Texas RE and NERC. See our NERC CIP guide.
How we help

How can ALCON DTS help you?

You keep the compliance decisions, and your own staff keep the ERCOT and PUCT contact roles. ALCON DTS supports the IT and security side of your program, working alongside your compliance team.

General illustrations of IT and security support, not PUCT or ERCOT requirements.
Area How ALCON DTS supports you
Emergency Operations Plan Drafting support for the IT portions of your cyber security annex, drill support for IT scenarios, and evidence organization
Cybersecurity monitor program Evidence organization for the IT side, if you choose to complete a voluntary self-assessment
Incident readiness Incident response planning and tabletop exercise support for IT scenarios
Vendor attestations Vendor inventories and vendor risk documentation that support your legal team’s attestations
Identity, patching and logging MFA, patch management and logging for corporate IT systems

Our Security Monitoring (SIEM) service and our Backup and Disaster Recovery service are each quoted on their own. The exact controls in your environment depend on your ALCON DTS plan and any project work, and our expert team will show you which controls are in place today and which would add coverage. Your organization keeps control of its compliance program, and ALCON DTS supports the IT and security side.

Related rules

How do Texas grid rules fit with other rules?

  • NERC CIP. Applies to NERC-registered entities with BES assets, alongside state rules. See our NERC CIP guide.
  • DOE-417. Federal electric emergency incident reporting has its own criteria and timelines. See the DOE-417 Form Instructions.
  • Texas Grid Security Commission. Texas is studying new grid resilience standards (SB 75, 2025). Its role is to recommend resilience standards and an all-hazards plan to the legislature, due by December 1, 2026 (PURA 44.005, 44.007).
  • Texas Electric Grid Security Council. An advisory body for best security practices (PURA 39.917).
  • Weather emergency preparedness. 16 TAC 25.55 sets weatherization duties for ERCOT, generation entities and transmission service providers in ERCOT.
  • Energy and Utilities overview. Rules by type of organization, including Texas breach notice and the SB 2610 safe harbor. See Energy and Utilities.
Questions

Frequently asked questions

Transmission and distribution utilities, PURA 32.053 corporations, and munis or co-ops that own or operate ERCOT transmission at 60 kV or more.

No. The statute says it “does not grant enforcement authority to the cybersecurity monitor,” and self-assessments are voluntary.

The filing is due by March 15 every year, with the full plan at least once every three years. The plan includes a cyber security annex and a physical security incident annex.

No. It is a proposed revision to ERCOT’s cybersecurity incident notice rules.

No. Its role is to recommend resilience standards and a plan to the legislature, due by December 1, 2026.
Services

Related services

Sources

Sources

Last reviewed: October 27, 2026

This page is general information about Texas grid cybersecurity rules, not legal advice for your situation.

Next step

Talk with ALCON DTS about Texas grid cybersecurity

Want a clearer picture of the IT side of your Texas grid program? Our expert team will walk through your environment with you, show you the controls in place today and suggest next steps for the IT side.