Rogue or Unsecure AP Detected

Rule ID

PH_Rule_PolicyViolation_14

Default Status

Enabled

Description

Detects a rogue or unsecure AP association attempt

Severity

MITRE ATT&CK® Tactics

Initial Access

Initial Access consists of techniques that use various entry vectors to gain their initial foothold within a network. Techniques used to gain a foothold include targeted spearphishing and exploiting weaknesses on public-facing web servers. Footholds gained through initial access may allow for continued access, like valid accounts and use of external remote services, or may be limited-use due to changing passwords.

https://attack.mitre.org/tactics/TA0001

MITRE ATT&CK® Techniques

No Technique Specified

Impacts

Network

Data Source

Aruba WLC via SNMP Trap, Cisco WLC via SNMP Trap; SonicWall Firewall via Syslog

Detection

Correlation

Remediation Guidance

No remediation guidance specified

Time Window

If the following pattern or patterns match an ingested event within the given time window in seconds, trigger an incident.

600 seconds

Trigger Conditions

If the following defined pattern/s occur within a 600 second time window.

Rogue

SubPattern Definitions

SubPattern Name: Rogue

This is the named definition of the event query, this is important if multiple subpatterns are defined to distinguish them.

SubPattern Query

This is the query logic that matches incoming events

eventType IN ("Aruba-1053-wlsxUnsecureAPDetected","Aruba-1150-wlsxSuspectUnsecureAPDetected", "Aruba-1103-wlsxStaAssociatedToUnsecureAP","Cisco-WLC-36-bsnRogueAPDetected", "Cisco-WLC-59-bsnRogueAPDetectedOnWiredNetwork", "SonicOS-546")

Group by Attributes

This defines how matching events are aggregated, only events with the same matching attribute values are grouped into one unique incident ID

reptDevIpAddr,srcMACAddr

Aggregate Constraint

This is most typically a numerical constraint that defines when the rule should trigger an incident

COUNT(*) >= 1

Incident Attribute Mapping

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

 hostIpAddr = Rogue.reptDevIpAddr,
srcMACAddr = Rogue.srcMACAddr

FortiSIEM Rules