Equifax’s insider trading case showed a blackout list covered who was told, not who could work it out

On March 14, 2018, the SEC alleged that an Equifax executive deduced the company’s own breach from a cover story and sold his shares. The case tested whether incident trading controls reached people who could infer the news as well as people told it.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On March 14, 2018, the SEC alleged that an Equifax executive deduced the company’s own breach from a cover story and sold his shares. The case tested whether incident trading controls reached people who could infer the news as well as people told it.

  1. The week On Wednesday, March 14, 2018, the Securities and Exchange Commission charged a former chief information officer of a U.S. business unit of Equifax with insider trading.
  2. The told: a blackout for the people read in The complaint describes a conventional response.
  3. The tasked: incident work under a cover story The second group appears throughout the complaint.
  4. The inferrers: people who worked it out The third group is the one the case turned on.
  5. The transaction: where any of them would trade The fourth part is the point where all three groups meet the market.
  6. How this applies across financial organizations A listed bank holding company files periodic reports and has insiders trading its shares.
  7. Objections One objection is that the case involved an unusually senior person with crisis training and a candid trail of messages.
  8. With hindsight Both Equifax trading matters ended in guilty pleas in the parallel criminal cases.

The week

On Wednesday, March 14, 2018, the Securities and Exchange Commission charged a former chief information officer of a U.S. business unit of Equifax with insider trading. The SEC said the trading came before the company’s September 2017 announcement of a data breach. Its release described the breach as exposing Social Security numbers and other personal information of about 148 million U.S. customers.

The SEC’s release set out the core allegation. It said the executive, who was next in line to be the company’s global CIO, allegedly used confidential information entrusted to him to conclude that Equifax had suffered a serious breach. It alleged that before public disclosure he exercised all his vested stock options and sold the shares, for proceeds of nearly $1 million. By selling before disclosure, the SEC alleged, he avoided more than $117,000 in losses.

The same day, the U.S. Attorney’s Office for the Northern District of Georgia announced parallel criminal charges. The SEC’s complaint, filed in federal court in Atlanta, charged violations of the antifraud provisions of the securities laws. It sought disgorgement with interest, penalties, an injunction and a bar from serving as an officer or director of a public company.

The complaint’s account of the company’s response is what makes the case useful to other organizations. What follows is the SEC’s account, as alleged. On July 29, 2017, the company’s security department observed suspicious network traffic tied to its consumer dispute portal. It blocked the traffic and, the next day, took the portal offline. On August 2, the company retained the cybersecurity group of a law firm and, through the law firm, engaged a forensic firm.

Under its internal policies, the company classified the event as a critical incident and formed a crisis action team of security, legal and IT staff. It named the response Project Sierra. Team members were told the information was confidential and was not to be shared outside the crisis action team. When forensic investigators found it likely that consumers’ personal information had been stolen, the company instituted a special trading blackout for those working on Project Sierra.

The response needed more people than the team. Between August 12 and 15, according to the complaint, Project Sierra members changed administrative credentials for hundreds of internal databases. That work required help from a broader group of IT employees who were not told of the breach.

The company also set up a notification and remediation effort called Project Sparta. It covered a consumer website, protective tools and call centers. The complaint says Project Sparta was kept separate from Project Sierra to limit the number of people who knew that the company itself had been breached. Staff working only on Project Sparta were told they were working for an unnamed client that had experienced a large breach.

The complaint then describes how the executive came to know. On Friday, August 25, 2017, an email to IT staff and business unit CIOs described a “VERY large breach opportunity” that needed a dramatic increase in system capacity. A meeting invitation that afternoon asked participants to prepare their applications for about 10 million customers. The complaint alleges that the executive, after a call with the global CIO and further signals that evening, concluded his own employer was the victim.

On the morning of Monday, August 28, the complaint alleges, he searched the internet for the effect of a 2015 breach at another credit bureau on that company’s stock price. Within an hour, it says, he exercised his vested options through his company-sponsored stock plan account and sold the shares. According to the complaint, he was formally told of the breach on August 30 and instructed not to trade. The company announced the breach after the market closed on September 7, 2017. On September 8, the complaint says, its stock fell nearly 14 percent.

The case came after the Commission’s February 21, 2018 interpretive guidance on cybersecurity disclosure. That guidance reminded companies and insiders that information about cybersecurity incidents may be material nonpublic information. It said companies should consider whether and when to restrict insider trading while investigating significant incidents.

Insider trading cases can look like stories about one person’s bad judgment. We read the March 2018 complaint as an operations document. It describes, in unusual detail, how a public company divided its incident response into people who knew and people who did not. It then alleges that one person on the outside of that line worked out the truth from the work he was asked to do.

That matters for any listed financial institution, and for any organization whose staff could trade on what an incident reveals. A bank holding company, a broker-dealer or an insurer with listed shares is likely to run an incident response of the same kind. Its trading controls depend on knowing who holds the information. The complaint shows that the answer is larger than the list of people who were told.

We take the problem in four parts. The first three are the groups of people an incident creates, and the fourth is the point where any of them would trade. Together they cover everyone who could act on the news before it is public:

  • The told: the people formally read into the incident, who were placed on a special blackout.
  • The tasked: the people asked to do incident work under a cover story or without explanation.
  • The inferrers: the people who saw enough signals to work out what was happening without being told.
  • The transaction: the moment any of these people places a trade, and the controls that apply there.

Our argument is that the blackout in the complaint protected the first group and the case turned on the third. A trading control built around a list of who was told will miss people who can infer. The controls that work against inference sit at the transaction, not on the list. After the four parts we look at how this differs across financial organizations, at objections, and at what a leader could check.

A note on sources. The account of Equifax’s internal response comes from the SEC’s complaint, which sets out allegations. The company was not charged in this case. We use the complaint for what it describes about the structure of a response, and we rely on the later releases of the SEC and the U.S. Attorney’s Office only for the outcome of the trading charges.

The told: a blackout for the people read in

The complaint describes a conventional response. The company classified the event under its policy, formed a crisis action team and gave the work a code name. Members were instructed that the information was confidential within the team. When investigators concluded that personal data had likely been stolen, the company imposed a special blackout for people working on Project Sierra.

Why the trigger mattered

The complaint ties the blackout to a finding: likely theft of consumers’ personal information. Before that finding, the team was investigating suspicious activity. After it, the team held information that, in the SEC’s view, was material. The timing of the special blackout tracked the moment the facts became serious.

The trigger is sensible, and it has a gap. An investigation can be sensitive before its conclusion is known. The February 2018 guidance spoke to this period directly. It said companies should consider whether and when to restrict trading “while companies are investigating and assessing significant cybersecurity incidents, and determining the underlying facts, ramifications and materiality.”

What the February guidance asked

The Commission’s February 21, 2018 guidance had addressed this group before the March 14 charges. It said information about a company’s cybersecurity risks and incidents may be material nonpublic information. It said directors, officers and other insiders would violate the antifraud provisions if they traded in breach of their duty while in possession of it.

The guidance went further than a reminder. It said insider trading policies that include prophylactic measures can protect against trading before public disclosure of an incident. It said companies would be well served by considering how to avoid the appearance of improper trading in the period after an incident and before disclosure. The language was advisory. It described a period, not a list of people.

Our reading is that the guidance’s period-based framing fits the problem better than a list. A period applies to whoever trades within it. A list applies only to whoever is on it. The Equifax complaint shows what falls between the two.

Who belongs on the list

A crisis action team of security, legal and IT staff is the obvious core. The complaint shows the list growing as the response grew. On August 23, 2017, it says, the CIO of another business unit was told of the breach and asked to lead the notification and remediation work. On August 30, the executive in this case was told and became part of Project Sierra.

Each addition was a decision someone made. The list of the told is therefore a record that can be kept: name, role, date read in, date of trading instructions. The complaint shows that the company had a process for reading people in. It describes an attorney giving the newly told executive a set of instructions developed for that situation, including not to trade.

Outside firms are on the list too

The complaint describes two outside firms in the first days. On August 2, 2017, Equifax retained the cybersecurity group of an Atlanta law firm to investigate and advise. The same day, through the law firm, it engaged an independent forensic consulting firm. Those firms held the same facts as the crisis action team.

Outside firms bring their own staff, their own systems and their own trading rules. A company cannot place a law firm’s or forensic firm’s employees on its own blackout. It can confirm that each firm’s engagement terms carry confidentiality obligations and that the firm restricts its people from trading in the client’s securities. For a financial institution, the same applies to the incident response retainer, the communications firm and any breach notification vendor.

The told list therefore has two parts. One names the institution’s own people. The other names the outside firms read in, with the date and the contractual basis for their confidentiality. Without a record kept at the time, the second part has to be rebuilt from invoices after the fact.

When the special blackout ends

A special blackout also needs an end. In the complaint’s account, Equifax announced the breach after the market closed on September 7, 2017, and the stock fell on September 8. A blackout that lifts at the announcement lets insiders trade into a market still absorbing the news. An insider trading policy can set a waiting period after earnings for this reason. An incident blackout needs a stated end that follows the same logic.

Operational detail

For a listed financial institution, the told list belongs to the incident commander and the legal function jointly. Security knows who is working the incident. Legal knows which facts are sensitive and when a special blackout applies. The corporate secretary or compliance officer who administers the insider trading policy needs the names on the day they are added.

An examiner or auditor reviewing the response afterward would want to see the list with dates. They would compare it with trading records for the same period. A response without that list leaves the organization reconstructing it from emails and calendars, after the fact and under scrutiny.

The tasked: incident work under a cover story

The second group appears throughout the complaint. The response needed capacity, credentials changed and a consumer program built. Each of those tasks pulled in people outside Project Sierra. The company chose not to tell them, and in one case gave them a cover story.

Two kinds of tasked staff

The complaint identifies two kinds. The IT employees who helped change administrative credentials for hundreds of databases between August 12 and 15 were not informed of the breach. The Project Sparta staff building the consumer response were told they were working for an unnamed client.

Both choices protected the information in a narrow sense. Fewer people were told. Both also created a population doing work whose nature pointed toward the truth. Changing credentials across hundreds of databases at short notice is unusual work. Building breach response capacity for a client in the same industry, at a scale of millions, is unusual too.

Why cover stories leak

A cover story has to be consistent with the work it explains. The complaint describes requests that strained that consistency. The capacity requirement was large and urgent. Senior executives were canceling travel. A senior crisis manager was asking for database logs. In the complaint’s account, each was a fact the executive could connect.

The second case, filed on June 28, 2018, shows the same pattern from lower in the organization. The SEC said a software engineering manager was creating a website for consumers affected by a breach. It said he was told the work was for an unnamed potential client, but concluded from information he received that Equifax itself was the victim. He bought put options, the SEC alleged, in violation of company policy.

Emergency changes as a signal

The credential work deserves its own note. Changing administrative credentials for hundreds of internal databases over a few days, as the complaint describes, generates change tickets, approvals and outage notices. The IT staff who executed the work were not told why. The record of the work, however, existed in the company’s own systems.

For a financial institution, the equivalent is an emergency change window that touches a large set of systems at once. Change management staff, system owners and on-call engineers all see it. A large unscheduled credential rotation is the kind of event an experienced engineer reads as a response to compromise. Our view is that the change approvers for such work belong in the tasked group.

Remediation at scale

Project Sparta, as the complaint describes it, was a consumer program: a website where consumers could check whether they were affected, a suite of protective tools and staffed call centers. The company decided to run much of it through its own Global Consumer Solutions business unit. Remediation programs of that kind draw in product, engineering, operations and customer service staff.

For a bank or insurer, the equivalent programs are notification letters, call center scripts, credit monitoring arrangements and card reissuance. Each pulls in a different function and, in some cases, a vendor. The number of people doing remediation work can be far larger than the crisis team. Their work also reveals scale, which is one of the facts that make an incident material.

That scale is what the August 25 meeting invitation conveyed, in the complaint’s account: prepare for about 10 million customers. A capacity figure in a work request is itself sensitive information. Our reading is that the people who receive such a figure belong in the tasked group for trading purposes, even if they are told nothing else.

What the tasked group needed

Our reading is that the tasked group needed a trading restriction without needing the facts. A company can tell employees that they are working on a confidential matter and may not trade in the company’s securities until told otherwise. That instruction reveals that something sensitive is under way. It does not reveal what.

The trade-off is a signal. A broad restriction tells a wide group of employees that something significant is happening, and that knowledge can itself travel. Our view is that the signal is a smaller risk than a group of employees free to trade while doing work that points to the answer. Organizations should weigh that with counsel, since the right breadth depends on the facts.

Operational detail

The tasked group is hard to list because it forms through ordinary work requests. The incident commander knows when the response pulls in a new team. Project managers know who is staffed on a work stream. A practical control is to require that any work request originating from the incident carry a code that triggers a trading instruction for the people assigned.

Vendors complicate the picture. A remediation program may engage call center firms, mail houses and credit monitoring providers. Their staff see the volume and timing of the work. They are not employees and are not on the company’s trading policy. Their engagement terms are the only lever, and the instruction has to be in place before the vendor’s staff see the scale of the work.

That control has costs. It slows urgent work slightly. It requires the people raising requests to remember the rule under pressure. It also creates more records to reconcile. Those costs are visible in advance, which is better than discovering the gap in an investigation.

The inferrers: people who worked it out

The third group is the one the case turned on. The executive was not on the told list on August 25, according to the complaint. He was on the edge of the tasked group, as a CIO whose systems had to absorb the capacity request. The SEC alleged that he moved from tasked to knowing by inference.

What the signals were

The complaint lists the signals as the SEC saw them. There was the request itself, described as a breach opportunity at large scale. There was a call with his superior, who told him he did not need to know why yet. There were messages that evening about canceled travel by the chief security officer, the chief legal officer and a cybersecurity vice president. There was a request for database logs from crisis management staff.

The complaint adds context about his background. It says he had participated in crisis training that simulated a breach in which the CIO was unavailable and he stepped into the role. Someone with that preparation, the SEC’s account implies, was well placed to recognize a real breach response from its outline.

The choice not to explain

One detail in the complaint deserves attention from anyone who manages people during an incident. When the executive called the global CIO with concerns about the request, the complaint says, he was told he was expected to comply. He was also told he did not need to know why yet, but would understand at some point.

That is a reasonable thing for a manager to say when facts must be contained. It also tells the listener that there is a reason worth withholding. Our view is that a manager who declines to explain incident work should pair the refusal with a trading instruction. The instruction costs nothing extra. It closes the gap that the refusal opens.

The SEC’s theory did not depend on anyone telling him directly. The complaint alleged that he used information entrusted to him by his employer to conclude that Equifax was the victim. It alleged that he owed a duty of trust and confidence and knew or was reckless in not knowing that the information was material and nonpublic.

We do not draw legal conclusions from a complaint, which contains allegations. The later outcome is a matter of record: he pleaded guilty in the criminal case. Our reading is that the case shows inference from entrusted information can be enough to create exposure. How that applies to a given organization’s staff is a question for its counsel.

The evidence comes from the company’s own records

The complaint’s account rests on records: text messages, emails, a calendar invitation, call times and internet browsing history. It quotes messages and lists search terms with timestamps. Whatever their source in this case, records of that kind are what an investigation reconstructs afterward.

For an organization, that has a practical consequence. Communications and device records from the incident period are evidence for the incident itself and for any trading inquiry that follows. A legal hold issued when the incident plan is activated should cover the tasked and inferring groups as well as the crisis team. Otherwise the records that matter for a trading question may be deleted under ordinary retention schedules.

Who can infer

Inference depends on position. Senior technology leaders see capacity requests, credential changes and unusual access patterns. Finance staff see emergency vendor engagements and unbudgeted spending. Executive assistants see canceled travel and new meeting series. Investor relations staff see requests to prepare holding statements.

These people do not need to be told for the pattern to be visible. The list of inferrers cannot be drawn with certainty, because it depends on what each person notices. It can be approximated by role. The roles that see the response’s footprint are the ones to cover.

Training cuts both ways

The complaint’s mention of crisis training points to a tension. Organizations train deputies to step into senior roles during a breach, which is good resilience practice. The same training teaches those deputies what a breach response looks like from the inside. They become the people best able to recognize one from its outline.

That is a reason to add a trading module to incident exercises. A tabletop that rehearses the technical and communications response can also rehearse the moment the insider trading administrator is notified. Participants then learn, before any real incident, that recognizing a response carries the same obligations as being told about one.

Operational detail

A role-based approach starts with the incident response plan. It names the functions that will be engaged in a significant incident: security, technology, legal, communications, finance, executive support. When the plan is activated at a defined severity, a trading instruction can go to everyone in those functions above a set level, whether or not they are read in.

Some organizations may already have a list that approximates this: the people subject to quarterly blackout periods around earnings. That list was built for financial information. Its fit with an incident’s footprint is a question to test, not to assume.

The transaction: where any of them would trade

The fourth part is the point where all three groups meet the market. Whoever knows, by being told, by being tasked or by inference, has to place a trade to profit. The trade passes through systems the company can see or govern.

What the complaint shows about the trade

The complaint says the executive exercised his vested options and sold the shares through his company-sponsored stock plan account at a brokerage firm. It says he did so within an hour of his internet searches on the morning of August 28, 2017. The transaction ran through an account the company sponsored and involved equity awards the company granted.

The company learned of the trading after the fact. The complaint says that when the executive was formally told on August 30, the attorney who briefed him was unaware he had already traded. It says he did not volunteer it. The global CIO offer made on September 15 was withdrawn after senior executives learned of the trading.

Equity awards concentrate the exposure

The complaint says the executive received part of his pay through stock option grants and restricted shares. It says that as of October 1, 2016, he held 6,815 vested options, which he kept until August 28, 2017. It says the sale produced proceeds of more than $950,000. The SEC’s release rounded that to nearly $1 million.

Technology and security leaders at listed financial firms can hold equity awards of that kind. The people best placed to infer an incident from its footprint may also hold sizable vested positions outside the executive suite. That combination is a reason to include senior technology roles in pre-clearance, whether or not they are designated insiders for earnings purposes.

Controls at the transaction

A trading control at the transaction does not depend on knowing who knows. Pre-clearance requires designated people to ask before trading. The person reviewing the request can check whether a sensitive matter is open. A company-sponsored stock plan can route exercises and sales by designated employees through a review step.

Those are design options, not requirements of any rule we cite. Their value in the Equifax facts is clear in hindsight. A pre-clearance request on the morning of August 28 could have reached someone who knew about Project Sierra. That person could then have declined it without explaining why. Whether any such control existed at Equifax, the complaint does not say.

Looking back at trades after every significant incident

A transaction control also works after the fact. Once an incident is disclosed, the compliance function can compare trades by designated people, and by the roles in the incident plan, against the incident timeline. The comparison covers the period from first detection to public disclosure.

The review has two uses. It finds trades that need explanation while the facts are fresh. It also tests the controls: if people outside the told list traded during the window, the list was too narrow. Equifax did conduct an internal investigation, according to the complaint, and concluded on October 16, 2017 that the executive had violated its insider trading policy. A standing after-action review makes that step part of every significant incident.

The plan defense and its later tightening

Trading plans are the other side of the transaction. The February 2018 guidance noted that its reminder would not preclude insiders from relying on Rule 10b5-1 if all its conditions were met. A trading plan adopted in good faith before any knowledge of an incident is a defense the rule recognizes.

The SEC tightened that defense in December 2022, as we describe in the hindsight section. For incident planning, the relevant point is that trades under a pre-existing plan can continue during a response. A company should know which insiders have such plans before an incident, so that the legal team is not surprised by trades during one.

Operational detail

The transaction controls belong to the corporate secretary or the compliance officer who administers the insider trading policy, working with the stock plan administrator. The incident response plan should include a step to notify that person when the plan is activated. The notice need not describe the incident. It needs to say that pre-clearance requests from named functions should be held for legal review.

How this applies across financial organizations

Listed banks and bank holding companies

A listed bank holding company files periodic reports and has insiders trading its shares. Its incident response is likely to pull in technology, operations, legal and communications staff in the same way Equifax’s did. Its insider trading policy may cover officers and directors and a list of designated employees. The question is whether the incident plan connects to that policy on the day the plan is activated.

Broker-dealers and asset managers

A broker-dealer or asset manager that is itself listed faces the same issuer question. It also holds client information as part of its business. Firms that already maintain restricted and watch lists for client matters have machinery that could carry an incident code name. Whether their incident plan uses that machinery is a design choice to test.

The watch list approach has a limit worth naming. Watch lists in these firms track information about client issuers. An incident at the firm itself concerns the firm’s own securities, which may be governed by a separate employee trading policy. Linking the two requires a deliberate decision about who administers restrictions on the firm’s own stock during an incident.

Insurers and other listed financial firms

Insurers and listed payment firms are likely to run incident responses with the same structure. Their claims, payments and customer service functions are likely to be part of a remediation program like Project Sparta. Those staff are the tasked group in waiting.

For a listed insurer, the tasked group can also include claims adjusters and actuarial staff asked to estimate exposure from an incident at the insurer or at a policyholder. An estimate of incident cost prepared for management is the kind of figure that bears on materiality. The people who prepare it are positioned to infer, whatever they are told about its purpose.

Credit unions and privately held institutions

Credit unions and privately held banks have no listed equity of their own. The issuer question does not arise for their own shares. A different one can. Their incident teams may learn that a listed vendor or partner has been breached before the market does. Such news is information about another company. Counsel should review how staff trading policies treat information learned about third parties during an incident.

Public agencies and public finance

The issuer question can also reach public bodies, though differently. A public agency or a nonprofit health system that issues municipal bonds makes statements to investors through continuing disclosure. Its staff do not hold its equity. The trading risk is smaller, but the disclosure obligations around an incident can be real. Counsel for such issuers should confirm how an incident is assessed for investor disclosure.

Objections

That the facts were extreme

One objection is that the case involved an unusually senior person with crisis training and a candid trail of messages. An ordinary incident may not produce such a clear record. The point holds for the evidence. It does not change the structure. Every significant incident creates a tasked group and a set of people positioned to infer. The clarity of this record is what makes it useful as an illustration.

That broad restrictions leak the secret

A second objection is that telling large groups not to trade announces that something is wrong. We discussed this under the tasked group. The restriction reveals a sensitive matter without its content. Earnings blackouts already work this way, telling a wide group that numbers exist without disclosing them. An incident instruction can follow the same model.

That the 2023 disclosure clock solved the problem

A third objection is that the SEC’s 2023 rules shortened the window between knowledge and disclosure. Item 1.05 of Form 8-K is generally due four business days after a company determines an incident is material. That clock starts at the materiality determination, not at discovery. The investigation period before that determination, the period the Equifax complaint describes, is still there.

That the company’s choices were reasonable

A fourth objection is that Equifax’s response choices were defensible. Containing knowledge to a crisis team, using a code name and giving remediation staff a cover story all reduce the chance that the news leaks to the public before the company is ready. The complaint does not criticize those choices, and neither do we.

Our point is narrower. Each choice that limited knowledge also created people who did incident work without a trading instruction. The containment and the trading control are separate decisions. A company can make the first and still add the second.

That rank-and-file restrictions are hard to enforce

A fifth objection is practical. Engineers and call center staff may not hold company stock, may not know they are covered and may not read instructions sent during a crisis. All of that may be true for a given group. The second Equifax case involved a software engineering manager, not an executive, and the SEC said his trade violated company policy. A special restriction that reaches only senior staff would miss people in his position. The instruction can be short, and the record of sending it is useful whether or not anyone tests it.

A sixth objection is that insider trading is a legal matter. The complaint shows that the information moved through operational channels: capacity requests, credential changes, staffing and travel. Legal owns the policy. Operations owns the channels. The controls need both.

What a leader could check

  • Does the incident response plan include a step that notifies the insider trading policy administrator when it is activated at a set severity?
  • Is there a dated record of who was read into each significant incident, kept by the incident commander and legal together?
  • When incident work is assigned to people who are not read in, do they receive a trading instruction with it?
  • Which roles would see the footprint of a response, and are they subject to pre-clearance during one?
  • Does the stock plan administrator have a way to hold exercises and sales by designated people for review?

With hindsight

Both Equifax trading matters ended in guilty pleas in the parallel criminal cases. On June 28, 2018, the SEC charged a second employee, a software engineering manager. It said he had been told his work on a consumer website was for an unnamed potential client and had concluded that Equifax was the victim. The SEC alleged he bought put options and, after the announcement, netted more than $75,000. It said he had agreed to settle the civil charges, subject to court approval. The U.S. Attorney’s Office later reported that he pleaded guilty on July 23, 2018.

The former CIO’s case concluded the following year. On June 27, 2019, the U.S. Attorney’s Office for the Northern District of Georgia announced his sentence. It said he had been convicted on March 7, 2019, after pleading guilty. He was sentenced to four months in prison and one year of supervised release, ordered to pay restitution of $117,117.61 and fined $55,000. The office described him as the second Equifax employee found guilty of insider trading relating to the breach.

The rules around insider trading then changed. On December 14, 2022, the SEC adopted amendments to Rule 10b5-1 and new disclosures. The amendments added cooling-off periods before trading can begin under a plan for persons other than issuers, and a good faith condition. Directors and officers must certify, when adopting or modifying a plan, that they are not aware of material nonpublic information. The amendments restricted overlapping plans and single-trade plans.

The same release required more disclosure about issuers’ insider trading policies and procedures, and quarterly disclosure of directors’ and officers’ use of trading plans. Issuers had to comply in the first periodic filing covering the first full fiscal period beginning on or after April 1, 2023, with a later date for smaller reporting companies. A listed company’s insider trading policy thus became a document investors could read. The release also required disclosure of policies on the timing of option grants relative to the release of material nonpublic information. Awards made in a window around certain filings that disclose such information go in a new table.

One more number shows how the public account of the breach itself changed. The complaint recounted that Equifax’s September 7, 2017 announcement said approximately 143 million U.S. consumers were potentially affected. The SEC’s March 2018 release referred to about 148 million.

On July 26, 2023, the SEC adopted cybersecurity disclosure rules. A material incident must be disclosed under new Item 1.05 of Form 8-K, generally within four business days after the company determines it is material. New Regulation S-K Item 106 requires annual description of processes for assessing, identifying and managing cybersecurity risks, and of board oversight and management’s role.

What held up from 2018 was the structure the complaint exposed. A response divides people into those told, those tasked and those who might infer. The February 2018 guidance had asked companies to consider trading restrictions during the investigation, before materiality is settled. The 2023 rules put a clock on disclosure after the materiality determination. They did not shorten the investigation that precedes it, which is the window the Equifax cases arose in. The 2022 disclosure requirement for insider trading policies made it easier for an outsider to see whether a company’s policy addresses that window.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • insider trading
  • incident response
  • trading blackout
  • Equifax
  • SEC
  • Rule 10b5-1