News Reported – not yet confirmed Security news
USDA resets database passwords and takes apps offline after a breach
The US Department of Agriculture (USDA) is dealing with a security incident its security operations centre uncovered early this week, according to Nextgov/FCW. IT staff are resetting every database password, which has left applications intermittently offline for days - including tools used for payments to farmers.
Key points
- According to Nextgov/FCW, an internal email sent on Monday says USDA's security centre uncovered an incident and IT must reset all database passwords in all environments.
- Outages hit financial tools for payments between the department and farmers, and apps where clients track loans and aid. USDA and CISA have not commented.
The US Department of Agriculture (USDA) is handling a security incident that has kept its applications offline for several days, according to Nextgov/FCW. The outlet based its report on an internal email, a technical bulletin and three people familiar with the matter. We have not yet found a public statement from USDA or from the US Cybersecurity and Infrastructure Security Agency (CISA).
What we know
- According to the email, sent on Monday 16 November, USDA's Cybersecurity and Privacy Operations Center uncovered the incident. It came from an acting assistant CIO at one of the department's business centres.
- The email says IT staff must "reset all database passwords in all environments", which means restarting the applications that depend on them. That is what is causing the outages.
- The outlet reports that the outages hit financial tools for payments between the department and farmers, and client-facing apps where people check notifications and the status of loans and aid. A technical bulletin dated Thursday warned of intermittent outages for the rest of the week, and some staff had VPN problems.
What we don't know
Who is behind the intrusion, how the attacker got in, whether data was taken and how long they were inside the network. USDA and CISA had not responded to the outlet's questions.
What to do now
- Admins: if you suspect a compromise, rotate database, service and application account passwords as well. Credentials sitting in configuration files and connection strings are a favourite target.
- Plan for the outage. A mass password reset means restarting applications - keep a map of which app uses which account, and a way to roll out new credentials without hunting for them by hand.
- Keep application credentials in a secrets vault with rotation, not in config files. Rotation then takes minutes rather than days.
Sources
Spotted a mistake? Let us know and we will correct it openly.