DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Jack Teixeira’s February 2022 Logs. Why wasn’t the insider threat prevented or detected?

Posted on April 29, 2023 by Dissent

Over on EmptyWheel, natsec journalist and blogger Marcy Wheeler writes, “In a motion to keep Jack Teixiera jailed, the government provided more details about what an unstable nut they gave access to the US’ most sensitive secrets.”

Read Marcy’s post.

Reading the logs from the perspective of someone who has blogged about insider threats and data breaches but who is not a national security expert, one wonders how the government either missed, underestimated, or just willfully ignored so many red flags. Over on JustSecurity, a number of experts commented on the case two weeks ago. One was  Erik Dahl, associate professor of national security affairs at the Naval Postgraduate School and faculty member of the Center for Homeland Defense and Security. He wrote:

From what we know so far, this appears to be a case of a knucklehead with a clearance, and such a person can be much more difficult to detect and track than traditional leakers, who are typically motivated by factors such as ideology, politics, or money.

Counterintelligence efforts can detect internal threats such as leakers at three different stages. First, before the person is granted a clearance and access to secrets, the security investigation and clearance approval process is designed to detect potential danger signs from someone’s past behavior and statements. Second, while the person is working in a position of trust — whether as a member of the military, a civilian employee, or a contractor — there are systems such as periodic clearance reviews designed to spot warning signs that might develop. And third, security systems are in place to detect loss of classified material and other internal threats as soon as possible, in order to contain the threat and identify the persons responsible.

All of these security systems are designed to detect traditional threats, such as insiders who voice extremist or violent views or who communicate with known terrorist groups or foreign security services. And all three of these systems appeared to have failed in this case, in which the offender appears to have been a low-level insider with no ideological or political axe to grind, and who was not motivated by traditional factors such money.

So how will lessons be learned and adopted from this incident?

Read more at JustSecurity.

 

No related posts.

Category: Government SectorInsiderU.S.

Post navigation

← Waterloo Region District School Board retirees say they felt left in the dark after data compromised in cyberattack
BakerHostetler’s 9th annual Data Security Incident Response Report →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure
  • Kentfield Hospital victim of cyberattack by World Leaks, patient data involved
  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.