Article Details
Scrape Timestamp (UTC): 2024-02-16 07:47:33.395
Source: https://thehackernews.com/2024/02/us-state-government-network-breached.html
Original Article Text
Click to Toggle View
U.S. State Government Network Breached via Former Employee's Account. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has revealed that an unnamed state government organization's network environment was compromised via an administrator account belonging to a former employee. "This allowed the threat actor to successfully authenticate to an internal virtual private network (VPN) access point," the agency said in a joint advisory published Thursday alongside the Multi-State Information Sharing and Analysis Center (MS-ISAC). "The threat actor connected to the [virtual machine] through the victim's VPN with the intent to blend in with legitimate traffic to evade detection." It's suspected that the threat actor obtained the credentials following a separate data breach owing to the fact that the credentials appeared in publicly available channels containing leaked account information. The admin account, which had access to a virtualized SharePoint server, also enabled the attackers to access another set of credentials stored in the server, which had administrative privileges to both the on-premises network and the Azure Active Directory (now called Microsoft Entra ID). This further made it possible to explore the victim's on-premises environment, and execute various lightweight directory access protocol (LDAP) queries against a domain controller. The attackers behind the malicious activity are presently unknown. A deeper investigation into the incident has revealed no evidence that the adversary moved laterally from the on-premises environment to the Azure cloud infrastructure. The attackers ultimately accessed host and user information and posted the information on the dark web for likely financial gain, the bulletin noted, prompting the organization to reset passwords for all users, disable the administrator account as well as remove the elevated privileges for the second account. It's worth pointing out that neither of the two accounts had multi-factor authentication (MFA) enabled, underscoring the need for securing privileged accounts that grant access to critical systems. It's also recommended to implement the principle of least privilege and create separate administrator accounts to segment access to on-premises and cloud environments. The development is a sign that threat actors leverage valid accounts, including those belonging to former employees that have not been properly removed from the Active Directory (AD), to gain unauthorized access to organizations. "Unnecessary accounts, software, and services in the network create additional vectors for a threat actor to compromise," the agencies said. "By default, in Azure AD all users can register and manage all aspects of applications they create. These default settings can enable a threat actor to access sensitive information and move laterally in the network. In addition, users who create an Azure AD automatically become the Global Administrator for that tenant. This could allow a threat actor to escalate privileges to execute malicious actions." ⚡ Free Risk Assessment from Vanta Generate a gap assessment of your security and compliance posture, discover shadow IT, and more.
Daily Brief Summary
An unnamed U.S. state government entity suffered a network breach via an admin account of a former employee.
Compromised credentials, discovered in a public leak database, allowed threat actors to access a virtual private network and blend in with legitimate traffic.
The attackers obtained additional credentials from a virtualized SharePoint server, further compromising the on-premises network and Azure Active Directory environment.
While no lateral movement to the Azure cloud was detected, host and user data were accessed and posted on the dark web.
Following the breach, immediate measures included password resets, the disabling of the compromised accounts, and reinforcement of privileged account security.
The lack of multi-factor authentication (MFA) on the compromised accounts was a significant security oversight.
The incident demonstrates the dangers of inadequately managed Active Directory accounts, including those of former employees.
Recommendations include implementing the principle of least privilege, using separate admin accounts for on-premises and cloud environments, and altering default Azure AD application registration settings to prevent unauthorized privilege escalation.