All news

16 November 2026 / 6 minutes of reading

An Attacker Got One Password. How Far Can They Get Inside Your Company?

A single stolen password, supplier account or exposed API key can open the way to critical systems. Find out how far an attacker can get when permissions, segmentation and monitoring fail.


A stolen password, supplier account or exposed API key does not necessarily mean that an attacker can take control of an entire organisation. But when combined with excessive permissions, weak segmentation and insufficient monitoring, it can open the way to critical systems.

An attack may begin with a phishing email, a fake job interview or an access token left in a public repository. However, attackers rarely want to remain inside a single employee’s inbox or on the first compromised device. They want to know which systems they can reach, what additional privileges they can obtain and whether anyone will detect their activity.

An organisation’s security therefore cannot be assessed solely by counting vulnerabilities or security tools. What also matters is whether individual weaknesses can be combined into a complete attack path. In its 2026 security report, Microsoft warns that attackers are increasingly exploiting trusted identities, systems, services and relationships between organisations. According to its data, publicly exposed cloud systems were compromised within an average of just 5.3 hours.

One account can open several more doors

Imagine an attacker obtaining the credentials of an external technician. The company protects the account with a password and multi-factor authentication, but once the technician signs in, the account has persistent access to several parts of the environment. Its permissions have not been reviewed for years because the account works and the supplier uses it regularly.

The attacker explores the available internal services and finds a configuration file containing a service password in shared storage. They use it to access another system, obtain higher privileges and gradually move into the production environment. Each weakness may appear relatively minor on its own. Together, however, they create a path to a critical target.

In a bank, this could provide access to internal applications, payment systems or customer data. In a hospital, the attack could affect systems required to provide healthcare. A MedTech company could lose source code, patient data or control over its cloud platform. In a manufacturing company, the attacker could reach operational technology, while in a SaaS business they could gain access to the production environment or customer data.

Attackers do not care whether a system belongs to the IT department, developers, facilities management or an external supplier. They follow the path of least resistance.

MFA protects the login, not the entire organisation

Multi-factor authentication significantly reduces the risk of a stolen password being misused. However, it does not guarantee that a compromised identity cannot be exploited. Attackers may persuade the victim to approve a login, steal an existing session token or misuse a service account or API key that is not protected by MFA.

Even a successful login does not have to result in a critical incident if the user has minimal permissions, access is time-limited and individual parts of the environment are properly separated. The risk increases when a compromised identity is combined with shared passwords, excessive privileges, forgotten accounts, exposed service interfaces or inadequate monitoring.

An attack can be stopped by any of several defensive layers: authentication, access management, segmentation, sensitive data protection, monitoring or the security team’s response. If each of these layers fails, a single compromised account may eventually lead to the takeover of critical systems.

The shortest route may lead through a supplier

External partners routinely manage cloud services, applications, medical devices, network infrastructure, manufacturing technology and physical security systems. Their work requires remote and often privileged access. However, an organisation may not have a complete overview of which supplier accounts still exist, who uses them and which systems they can reach.

Shared accounts, passwords that are not regularly rotated and access that remains active after a contract ends pose particular risks. One supplier may also serve several clients. Compromising the supplier’s environment can therefore give an attacker access to multiple organisations at once.

A November warning from Singapore’s Cyber Security Agency also highlighted an increase in attacks exploiting publicly accessible and unpatched systems, poorly protected identities and supplier access. The agency recommends separating third-party access from critical environments and regularly assessing the security of external providers.

Companies should therefore create a separate account for each supplier, limit its permissions and validity, and log all activity performed through it. Access should be revoked immediately when the relationship ends. It is also important to understand whether a compromised supplier account would allow an attacker to move into other parts of the environment.

An audit confirms the rules. A practical test confirms their effectiveness

An organisation may have MFA, an approved access management policy and documented network segmentation. An audit verifies whether these controls exist and are used according to established rules. However, it may not reveal what happens after a specific account is compromised or whether individual security controls can be bypassed in practice.

Penetration testing examines an agreed application, system or part of the infrastructure. Testers determine whether a publicly accessible service can be exploited, whether privileges can be escalated and whether one system can provide access to sensitive data or other parts of the network.

If an organisation needs to test the attacker’s entire path to a critical target, including people, identities, technologies and the security team’s response, Red Teaming is the appropriate approach. It does not simply identify existing vulnerabilities. It also determines whether an attacker can combine them, remain undetected and achieve a defined objective.

In both cases, the company needs more than a list of technical flaws. The results should show which weaknesses can actually be exploited, what their impact would be and what must change to stop the attack before it reaches critical systems.

Do you know what an attacker could achieve with one compromised account?

A stolen password, supplier account or exposed API key can be the beginning of an attack path leading to critical applications, sensitive data or operational technology. Citadelo will test where an attack could begin, how far an attacker could get and which security controls could stop them.

logo

Sign up for our newsletter for all the important cybersecurity and ethical hacking news.

© 2026 citadelo AG. All rights reserved.

facebooklinkedinxyoutube