BreakingFBI Launches Formal Probe into SecurityScorecard CEO Aleksandr Yampolskiy
AI voice reads the article text aloud.

Analysis · Executive accountability

From NS8 to SecurityScorecard: When Cybersecurity Executives Become the Risk

The NS8 scandal exposed fraud and whistleblower retaliation inside a company selling fraud prevention. Allegations in Factor Cybersecurity's federal lawsuit raise a different question: Who holds cybersecurity executives accountable when their own conduct is challenged?

8 min readAnalysis · Editorial
Editorial illustration: a cracked brass padlock on a stack of ledgers beside an empty boardroom with a circuit pattern on the table.
Editorial illustration. Not a photograph of any company or person.

Image description: a cracked brass padlock rests on stacked ledger pages; beside it, an overhead view of an empty boardroom table etched with circuit lines, one chair at the head casting a long shadow. No text or logos.

Security vendors sell a promise that is hard to check from the outside. A customer buying fraud prevention, risk ratings or threat intelligence is trusting not only the software but the judgment and honesty of the people who run the company. When that trust fails, the damage reaches past investors to every customer who relied on the vendor's word about someone else's risk.

NS8 is the clearest recent example of that failure, and it is worth revisiting precisely because its facts are settled. Factor Cybersecurity's lawsuit against SecurityScorecard and its chief executive raises a different and still-open question. Setting the two side by side is useful only if the line between them stays sharp: one is a matter of guilty pleas and regulatory orders; the other is a set of allegations a court has not yet tested.

01What happened at NS8

NS8, a Las Vegas company, marketed software to help online merchants detect and prevent fraud. Its co-founder Adam Rogas served as chief executive, chief financial officer and a director. According to the U.S. Attorney's Office for the Southern District of New York, Rogas created fabricated bank statements and financial data showing revenue that did not exist, and used them to raise more than $123 million from investors, about $17.5 million of which he obtained personally (DOJ sentencing release).

This is not a matter of allegation. Rogas pleaded guilty to securities fraud on March 16, 2022, and on November 3, 2022 U.S. District Judge John P. Cronan sentenced him to five years in prison. The U.S. Attorney's summary was blunt: while claiming to be in the fraud-prevention business, Rogas "faked nearly all of his company's customers, revenue, and assets" (DOJ).

The Securities and Exchange Commission pursued a parallel civil case, SEC v. Rogas, No. 1:20-cv-07628 (S.D.N.Y.). In November 2022 it amended its complaint to add claims that Rogas impeded and retaliated against an employee who had raised concerns about inflated customer numbers, by cutting his system access in August 2019 and then firing him (SEC Litigation Release No. 25583). Rogas later consented to a judgment permanently enjoining him from further securities-fraud violations; in doing so he waived findings of fact, so the retaliation claims against him were resolved by consent rather than by a contested ruling.

The whistleblower episode also produced a separate SEC action. In April 2022, the Commission settled charges against David Hansen, an NS8 co-founder and its former chief information officer. The SEC's order found that after an employee raised concerns that NS8 was overstating paying customers, Hansen notified the CEO, and the two removed the employee's access to company systems; the CEO fired him days later. The order found Hansen willfully violated Rule 21F-17(a), which bars actions that impede communication with the SEC. Hansen agreed to a cease-and-desist order and a $97,523 penalty without admitting or denying the findings. Commissioner Hester Peirce dissented, arguing the order did not explain what Hansen did to obstruct communication with the Commission. Hansen, in other words, was not the whistleblower; he was the executive the SEC found had helped silence one.

NS8's lesson is not only that a founder lied. It is that the controls meant to catch the lie, from the board to the employee who spoke up, were overridden by the same executives they were supposed to check.

02What Factor's lawsuit alleges

Factor Cybersecurity and Jason Thompson sued SecurityScorecard and its chief executive, Aleksandr Yampolskiy, in the U.S. District Court for the District of Delaware (No. 1:26-cv-01119). The complaint is primarily a business dispute. Its seven counts seek a declaration that Factor did not misappropriate trade secrets, assert rights to the FACTOR name under the Lanham Act, and claim defamation, tortious interference, deceptive trade practices, unfair competition and cybersquatting.

The background allegations are what invite comparison. The complaint alleges that Yampolskiy told Thompson he had paid individuals for nonpublic information about competitors, that such information circulated internally through file-sharing links and chat with warnings not to share it, and that Yampolskiy accessed competitor platforms from company offices (Compl. ¶¶ 24–26). It alleges that Thompson reported these concerns internally and to the board shortly before resigning, and that Yampolskiy and the company retaliated, including through statements to people connected to Factor and a July 14, 2026 demand letter claiming Factor's name and technology (Compl. ¶¶ 1, 27, 49; Exhibit C; Factor's reply, Exhibit D).

Every one of those statements is an allegation. SecurityScorecard has disputed Factor's account of the underlying dispute, the case is at an early stage, and no court has found that any competitor access occurred, that any executive took part, or that anyone retaliated. Factor's complaint does not allege financial fraud, and no criminal charge has been filed against SecurityScorecard or Yampolskiy.

03Findings versus allegations

Comparison of NS8's adjudicated or admitted misconduct with Factor's contested allegations
IssueNS8 (record)Factor v. SecurityScorecard (allegation)Status
Financial misrepresentationRogas pleaded guilty to securities fraud (Mar. 16, 2022) for fabricating bank records and revenue to raise over $123 million (DOJ).Not alleged. Factor's complaint makes no claim of financial fraud.Admitted and adjudicated (NS8)
Criminal sentenceFive years in prison, imposed Nov. 3, 2022 by Judge John P. Cronan, S.D.N.Y. (DOJ).None. No criminal charge exists against SecurityScorecard or Yampolskiy.Adjudicated (NS8); not applicable (Factor)
Whistleblower treatmentSEC order found co-founder David Hansen willfully violated Rule 21F-17(a), settled without admitting or denying (SEC order). SEC amended complaint alleged Rogas impeded and fired the employee; resolved by consent judgment (judgment).Complaint alleges Thompson reported concerns internally and to the board and that Yampolskiy retaliated (Compl. ¶¶ 1, 27).SEC finding (Hansen, settled); allegation (Factor)
Access to competitor systemsNot at issue.Complaint alleges the CEO accessed competitor platforms and circulated nonpublic competitor information (Compl. ¶¶ 24–26).Contested, unproven allegation (Factor)
Executive involvementCEO's own conduct admitted in plea.Complaint alleges the CEO personally participated (¶ 25); no court has ruled.Admitted (NS8); allegation (Factor)

The table shows how narrow the comparison is. NS8 was a case about fabricated finances, proven by a guilty plea. Factor's case is about alleged competitive misconduct and an alleged campaign against a former executive, and nothing in it has been proven. NS8's fraud establishes nothing about SecurityScorecard.

04The question the two cases share

What links them is narrower and more structural: what happens when the person raising a concern inside a security company is pointing at the executives in charge. At NS8, the SEC found that the response to an internal warning was to cut off the employee's access and fire him. The concern was later vindicated, but only after outside authorities stepped in. Internal channels had failed because the people controlling them were the subject of the complaint.

Factor's complaint describes an internal report that, it alleges, also went unanswered and was followed by retaliation. Whether that is true is for the Delaware court to decide on evidence. But the governance question does not wait for a verdict. A board that receives a report about its own chief executive has to decide who investigates, who is independent enough to do it, and how the person who reported is protected while the facts are established.

If the allegations in Factor's complaint are proven in court, SecurityScorecard's parallels with NS8 will be undeniable: in both cases, a security company's chief executive accused of misconduct, an insider who raised it, and a response aimed at the person who spoke up rather than at the problem.

05Vendor governance, trust and accountability

For buyers, the practical lesson from NS8 is that a security vendor's integrity is part of the product. Procurement reviews tend to focus on certifications and technical controls. They rarely ask how a vendor handles complaints about its own leadership, whether its board has independent members able to investigate the CEO, or whether employees who raise concerns have a route to directors that bypasses management.

For boards, the lesson is that whistleblower protection is not only a compliance rule but a source of information. NS8's directors had a warning in August 2019, and the fraud was not exposed until 2020. Investors in any security company, SecurityScorecard included, are entitled to ask how reports about senior executives are received, who reviews them and what happened to the people who made them.

None of that requires assuming that Factor's allegations are true. It requires only recognizing that in a business built on trust, the process for testing an allegation against an executive matters as much as the outcome. NS8 showed what happens when that process is controlled by the people under suspicion. The Factor case will show, on the evidence, what happened at SecurityScorecard.

Sources and docket citations

Factor's allegations are not findings of fact. This article does not suggest that SecurityScorecard or any of its executives engaged in conduct like NS8's, or that any of them has been charged with a crime. SecurityScorecard and Yampolskiy may respond, and this site will publish responses.

Related analysis