Bill Forrest is the most frequent co-covered peer, appearing in 1 of the 3 tracked stories. Each story carries 2.3 original sources on average, compared with 3.2 for the broader beat in this window. That works out to roughly 0.1 stories per week across a 148-day span.
Figures are computed live from our source-verified story record
— see our methodology for how impact and
sentiment are derived.
What the coverage shows about Social Security Administration
Bill Forrest is the most frequent co-covered peer, appearing in 1 of the 3 tracked stories. Each story carries 2.3 original sources on average, compared with 3.2 for the broader beat in this window. That works out to roughly 0.1 stories per week across a 148-day span. Their average consequence score of 6.3 runs below the beat's 6.9 for that window. data-breach accounts for 1 of the 3 tracked stories, while 2 other categories carry the remainder. Social Security Administration appears in 3 tracked Cybersecurity stories published from March 11, 2026 through August 5, 2026.
Stories tracked
3
Per week
0.1
Sources per story
2.3
Computed from the 3 stories linked to this entity, with beat comparisons drawn from all 585 Cybersecurity stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Appears alongside
Other entities that clear the same relevance threshold in stories also covering Social Security Administration. Shared-story counts are live from our verified record — not editorial picks.
Bisignano claims he called Charlie Scharf the same evening and they 'had a good laugh' about the article; no independent confirmation of the call's content.
WSJ publishes investigation
The Wall Street Journal reports that Bisignano allegedly directed security staff to surveil colleagues' emails during his tenure at JPMorgan.
Congressional Response
Senators Ron Wyden and Richard Neal call for a full public accounting of the breach.
Investigation Confirmed
Federal oversight bodies confirm a formal probe into DOGE's data handling practices.
Public Disclosure
The Washington Post and The Independent report on the whistleblower allegations involving the DOGE staffer.
OIG Notification
SSA Office of Inspector General alerts lawmakers to an anonymous complaint regarding data misuse.
Internal Red Flags
SSA security officials report irregular data export patterns and access by unvetted personnel.
Data Access Requests
DOGE advisors request deep-level access to SSA earnings and identity databases.
DOGE Formation
The Department of Government Efficiency begins auditing federal agencies for waste.
Bisignano serves as co-COO
Frank Bisignano serves as co-chief operating officer at JPMorgan Chase from 2012 to 2013, the period during which the alleged email spying is said to have occurred.
Stories mentioning Social Security Administration 3
Allegations that Frank Bisignano, now IRS chief, spied on JPMorgan colleagues’ emails offer a stark insider threat case study. No customer data was breached, but the reported abuse of security staff reveals critical gaps in executive oversight of monitoring tools.
Federal authorities have initiated a formal investigation into the Department of Government Efficiency (DOGE) following allegations of unauthorized access and handling of sensitive Social Security Administration data. The probe centers on potential violations of the Privacy Act and federal cybersecurity protocols regarding the management of personal identifiable information.
A whistleblower complaint alleges a former Department of Government Efficiency (DOGE) employee exploited 'God-level' access to exfiltrate data on 500 million Americans from Social Security Administration databases. The staffer reportedly intended to share the data with a private employer and expressed confidence in receiving a presidential pardon for the actions.
Social Security Administration is linked from 3 stories on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source
link? Report a data issue.