Meanwhile, the purge continues.
>>>WASHINGTON, Feb 14 (Reuters) - The administration of U.S. President
Donald Trump has laid off about 1,200 to 2,000 workers at the Department of Energy, including employees at the nuclear security administration and the loans office, two sources familiar with the matter said on Friday. . . .
The two sources said the layoffs come after
three people representing billionaire
Elon Musk's Department of Government Efficiency arrived at the agency.
Some 325 workers have been let go from the department's National Nuclear Security Administration, which manages the U.S. nuclear weapons fleet and works to secure radiological materials around the world, one of the sources said.
"It's insane," the sources said, pointing out the losses at the NNSA occur at a time when nuclear power plants have been at risk in
Russia's war on Ukraine, including
Zaporizhzhia, the largest in Europe.<<< (emphasis added)
This article touches on a few of the issues:
>>>The employees at DOGE are
reportedly working seven days a week, on very little sleep. This slumber-party atmosphere isn’t a great fit for the sober and secretive world of nuclear weapons, where security lapses are hugely consequential. I spoke with three former officials and nuclear experts about what might happen if DOGE were to take a too-cavalier approach to the NNSA. None believed that Musk’s auditors would try to steal important information—although it is notable that not everyone at DOGE is a federal employee, many lack the security clearance to access the information they are seeking, and Musk had to be stopped from
hiring a noncitizen. Nuclear-security lapses don’t need to be intentional to cause lasting damage. “When access to the NNSA’s sensitive systems is not granted through proper channels, they can be compromised by accident,” the former senior official at the Department of Energy, who requested anonymity to discuss internal matters, told me. “You could stumble across some incredibly sensitive things if you are coming at it sideways.”<<<
The risk of messing with the wrong computer system
www.theatlantic.com