Rules: RDP with non-standard client
While the product_id of the RDP client is not required, a missing one or one that does not look like a client access license can indicate an RDP attack with hacker software (ie NCRACK, hydra).
| Detail | Value |
|---|---|
| Type | Match |
| Category | Lateral Movement |
| Apply Risk to Entities | device_hostname, device_ip, srcDevice_hostname, srcDevice_ip, user_username |
| Signal Name | RDP with non-standard client |
| Summary Expression | RDP connection with non-standard client from IP: {{srcDevice_ip}} to IP: {{dstDevice_ip}} |
| Score/Severity | Static: 2 |
| Enabled by Default | True |
| Prototype | False |
| Tags | _mitreAttackTactic:TA0008, _mitreAttackTactic:TA0011, _mitreAttackTechnique:T1219, _mitreAttackTechnique:T1021.001, _mitreAttackTechnique:T1021 |
| Origin | Field |
|---|---|
| Normalized Schema | bro_rdp_clientDigProductId |
| Normalized Schema | device_hostname |
| Normalized Schema | device_ip |
| Normalized Schema | srcDevice_hostname |
| Normalized Schema | srcDevice_ip |
| Normalized Schema | user_username |