|
|
|
CAPEC-577: Owner Footprinting |
Description An adversary exploits functionality meant to identify information about the primary users on the target system to an authorized user. They may do this, for example, by reviewing logins or file modification times. By knowing what owners use the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command that may accomplish this is "dir /A ntuser.dat". Which will display the last modified time of a user's ntuser.dat file when run within the root folder of a user. This time is synonymous with the last time that user was logged in. Likelihood Of Attack Typical Severity Prerequisites
The adversary must have gained access to the target system via physical or logical means in order to carry out this attack. |
Administrator permissions are required to view the home folder of other users. |
Consequences This table specifies different individual consequences associated with the attack pattern. The Scope identifies the security property that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in their attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.Scope | Impact | Likelihood |
---|
Confidentiality | Other | | Confidentiality Access Control Authorization | Bypass Protection Mechanism Hide Activities | |
Mitigations
Ensure that proper permissions on files and folders are enacted to limit accessibility. |
Taxonomy Mappings CAPEC mappings to ATT&CK techniques leverage an inheritance model to streamline and minimize direct CAPEC/ATT&CK mappings. Inheritance of a mapping is indicated by text stating that the parent CAPEC has relevant ATT&CK mappings. Note that the ATT&CK Enterprise Framework does not use an inheritance model as part of the mapping to CAPEC.Relevant to the ATT&CK taxonomy mapping (also see parent) Entry ID | Entry Name |
---|
1033 | System Owner/User Discovery |
Content History Submissions |
---|
Submission Date | Submitter | Organization |
---|
2015-11-09 (Version 2.7) | CAPEC Content Team | The MITRE Corporation | | Modifications |
---|
Modification Date | Modifier | Organization |
---|
2018-07-31 (Version 2.12) | CAPEC Content Team | The MITRE Corporation | Updated Attack_Motivation-Consequences, Attack_Prerequisites, Description Summary, References, Related_Weaknesses, Typical_Likelihood_of_Exploit, Typical_Severity | 2019-04-04 (Version 3.1) | CAPEC Content Team | The MITRE Corporation | Updated Related_Attack_Patterns | 2019-09-30 (Version 3.2) | CAPEC Content Team | The MITRE Corporation | Updated @Abstraction |
More information is available — Please select a different filter.
|