attack-pattern--09c4c11e-4fa1-4f8c-8dad-3cf8e69ad119.json

{
    "external_references": [
        {
            "source_name": "mitre-attack",
            "external_id": "T1110.001",
            "url": "https://attack.mitre.org/techniques/T1110/001"
        },
        {
            "external_id": "CAPEC-49",
            "source_name": "capec",
            "url": "https://capec.mitre.org/data/definitions/49.html"
        },
        {
            "source_name": "Cylance Cleaver",
            "description": "Cylance. (2014, December). Operation Cleaver. Retrieved September 14, 2017.",
            "url": "https://www.cylance.com/content/dam/cylance/pages/operation-cleaver/Cylance_Operation_Cleaver_Report.pdf"
        },
        {
            "source_name": "US-CERT TA18-068A 2018",
            "url": "https://www.us-cert.gov/ncas/alerts/TA18-086A",
            "description": "US-CERT. (2018, March 27). TA18-068A Brute Force Attacks Conducted by Cyber Actors. Retrieved October 2, 2019."
        }
    ],
    "created_by_ref": "The MITRE Corporation",
    "name": "Password Guessing",
    "description": "Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts. Without knowledge of the password for an account, an adversary may opt to systematically guess the password using a repetitive or iterative mechanism. An adversary may guess login credentials without prior knowledge of system or environment passwords during an operation by using a list of common passwords. Password guessing may or may not take into account the target's policies on password complexity or use policies that may lock accounts out after a number of failed attempts.\n\nGuessing passwords can be a risky option because it could cause numerous authentication failures and account lockouts, depending on the organization's login failure policies. (Citation: Cylance Cleaver)\n\nTypically, management services over commonly used ports are used when guessing passwords. Commonly targeted services include the following:\n\n* SSH (22/TCP)\n* Telnet (23/TCP)\n* FTP (21/TCP)\n* NetBIOS / SMB / Samba (139/TCP & 445/TCP)\n* LDAP (389/TCP)\n* Kerberos (88/TCP)\n* RDP / Terminal Services (3389/TCP)\n* HTTP/HTTP Management Services (80/TCP & 443/TCP)\n* MSSQL (1433/TCP)\n* Oracle (1521/TCP)\n* MySQL (3306/TCP)\n* VNC (5900/TCP)\n\nIn addition to management services, adversaries may \"target single sign-on (SSO) and cloud-based applications utilizing federated authentication protocols,\" as well as externally facing email applications, such as Office 365.(Citation: US-CERT TA18-068A 2018)\n\nIn default environments, LDAP and Kerberos connection attempts are less likely to trigger events over SMB, which creates Windows \"logon failure\" event ID 4625.",
    "id": "attack-pattern--09c4c11e-4fa1-4f8c-8dad-3cf8e69ad119",
    "type": "attack-pattern",
    "kill_chain_phases": [
        {
            "kill_chain_name": "mitre-attack",
            "phase_name": "credential-access"
        }
    ],
    "modified": "2020-10-19T22:43:45.126Z",
    "created": "2020-02-11T18:38:22.617Z",
    "x_mitre_contributors": [
        "Microsoft Threat Intelligence Center (MSTIC)"
    ],
    "x_mitre_data_sources": [
        "Authentication logs",
        "Office 365 account logs"
    ],
    "x_mitre_permissions_required": [
        "User"
    ],
    "x_mitre_detection": "Monitor authentication logs for system and application login failures of [Valid Accounts](https://attack.mitre.org/techniques/T1078). If authentication failures are high, then there may be a brute force attempt to gain access to a system using legitimate credentials.",
    "x_mitre_version": "1.1",
    "x_mitre_is_subtechnique": true,
    "x_mitre_platforms": [
        "Linux",
        "macOS",
        "Windows",
        "Office 365",
        "GCP",
        "Azure AD",
        "AWS",
        "Azure",
        "SaaS"
    ]
}