PH_Rule_Access_15C
Enabled
Detects excessive application logon failures - 5 consecutive failures in a 10 minute period. Application logsons include the one that may require authentication for accessing the authentication, such as HTTP, SNMP, FTP, POP3, IMAP etc.
6
Security
Credential Access
Credential Access consists of techniques for stealing credentials like account names and passwords. Techniques used to get credentials include keylogging or credential dumping. Using legitimate credentials can give adversaries access to systems, make them harder to detect, and provide the opportunity to create more accounts to help achieve their goals.
https://attack.mitre.org/tactics/TA0006T1110.001
Brute Force: Password Guessing
Adversaries with no prior knowledge of legitimate credentials within the system or environment may guess passwords to attempt access to accounts.
https://attack.mitre.org/techniques/T1110/001Application
Oracle Database Server via JDBC, Microsoft SQL Server via JDBC, IBM DB2 via JDBC
Correlation
Identify the source of the incident and the user and make sure that it is a legitimate attempt to log on to the system. Make sure it is not a cached credential from another system while the primary user has changed credential. Make sure there are no other incidents from the source host that may indicate malware trying to gain access to other systems. Make sure there are no vulnerabilities on the source and destination hosts.
If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.
600 seconds
If the following defined pattern/s occur within a 600 second time window.
ExcessMiscAppLoginFailure1 OR ExcessMiscAppLoginFailure2
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
srcIpAddr IS NOT NULL AND eventType IN (Group@PH_SYS_EVENT_AppLogonFailure) AND eventType NOT IN (Group@PH_SYS_EVENT_AAALogonFailure)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
srcIpAddr, reptDevName, reptDevIpAddr, user
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT (*) >= 5
Operator Rank: 0 Operator Type: OR
This operator defines the logic condition relating to the prior event subpattern clause and the following event subpattern clause
This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.
This is the query logic that matches incoming events
srcIpAddr IS NULL AND eventType IN (Group@PH_SYS_EVENT_AppLogonFailure) AND eventType NOT IN (Group@PH_SYS_EVENT_AAALogonFailure)
This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID
reptDevName, reptDevIpAddr, user
This is most typically a numerical constraint that defines when the rule should trigger an incident
COUNT (*) >= 5
This section defines which fields in matching raw events should be mapped to the incident attributes in the resulting incident.
The available raw event attributes to map are limited to the group by attributes and the aggregate event constraint fields for each subpattern
srcIpAddr = ExcessMiscAppLoginFailure1.srcIpAddr,
destIpAddr = ExcessMiscAppLoginFailure1.reptDevIpAddr,
user = ExcessMiscAppLoginFailure1.user,
incidentCount = ExcessMiscAppLoginFailure1.COUNT(*),
destName = ExcessMiscAppLoginFailure2.reptDevName,
destIpAddr = ExcessMiscAppLoginFailure2.reptDevIpAddr,
user = ExcessMiscAppLoginFailure2.user,
incidentCount = ExcessMiscAppLoginFailure2.COUNT(*)