Acquire Access: recognize the technique
What you are learning
Acquire Access means getting access that already exists, such as an account or remote-access connection, instead of creating a new way into the target. A successful login does not always mean the person logging in is the legitimate user. Defenders should look at where the login came from, which device was used, whether MFA changed, and what happened after the login.
- Explain Acquire Access in plain language.
- Identify evidence a defender could review.
- Choose a defensive action that fits the observed behavior.
Organizations often watch failed logins and exploit attempts, but misuse of valid credentials can look normal at first. Defenders should compare a login with the user's usual devices, locations, times, MFA history, and follow-on activity. Looking at several signals together helps avoid treating one unusual login as proof of malicious activity.
Use a repeatable web-testing method
Connect this ATT&CK training activity to the WSTG approach: establish expected behavior, identify the relevant attack surface, change one controlled input or observation at a time, compare the response with the baseline, and record evidence before drawing a conclusion.
For reconnaissance-oriented lessons such as T1595, treat reachability, exposed services, and observable application behavior as information gathering. A reachable service is evidence about exposure; it is not by itself proof of a vulnerability.
Open WSTG web security fundamentalsPractice Preparation
Use these lesson concepts for the ungraded practice activity below. You do not need outside research.
- After a suspicious successful login, review authentication logs, device/session information, MFA history, network/location context, and follow-on account activity.
- Ask whether the device, location, time, MFA behavior, and subsequent actions are consistent with the legitimate user's normal activity.
- Controls include MFA, conditional access, session monitoring, credential protection, and rapid revocation of suspicious sessions.
This is ungraded practice. Use the lesson material above; exact wording is not required. Identify three evidence sources a defender could review after a suspicious successful login. Then give one question that helps separate normal from suspicious access and two controls that reduce risk. No external target interaction is required.
Check your understanding
Answer the questions shown below. You must answer at least 2 correctly before marking this concept lesson complete.
Valid credentials do not always mean valid use. Check the context around a successful login. Defenders should confirm the context with more than one source before deciding that the activity is suspicious.
Useful evidence includes login and identity logs, VPN or remote-access logs, new-device records, unusual source networks, MFA resets, password-reset history, and endpoint activity after login. Compare the event with the user's normal behavior, verify the device and source, and review what happened next. Reduce risk with strong MFA, device trust, rapid credential revocation, least privilege, and monitoring for exposed credentials.