Detection rules › Panther
Zoom Meeting Passcode Disabled
Meeting passcode requirement has been disabled from usergroup
MITRE ATT&CK coverage
| Tactic | Techniques |
|---|---|
| Collection | T1125 Video Capture |
Rule body yaml
AnalysisType: rule
Filename: zoom_operation_passcode_disabled.py
RuleID: "Zoom.PasscodeDisabled"
DisplayName: "Zoom Meeting Passcode Disabled"
Enabled: true
LogTypes:
- Zoom.Operation
Tags:
- Zoom
- Collection:Video Capture
Severity: Low
Description: >
Meeting passcode requirement has been disabled from usergroup
Reports:
MITRE ATT&CK:
- TA0009:T1125
Reference: https://support.zoom.us/hc/en-us/articles/360033559832-Zoom-Meeting-and-Webinar-passcodes
Runbook: >
Follow up with user or Zoom admin to ensure this meeting room's use case does not allow a passcode.
SummaryAttributes:
- p_any_emails
Tests:
- Name: Meeting Passcode Disabled
ExpectedResult: true
Log:
{
"time": "2021-11-17 00:37:24Z",
"operator": "homer@panther.io",
"category_type": "User Group",
"action": "Update",
"operation_detail": "Edit Group Springfield - Personal Meeting ID (PMI) Passcode: from On to Off",
"p_log_type": "Zoom.Operation",
}
- Name: Meeting Passcode Enabled
ExpectedResult: false
Log:
{
"time": "2021-11-17 00:37:24Z",
"operator": "homer@panther.io",
"category_type": "User Group",
"action": "Update",
"operation_detail": "Edit Group Springfield - Personal Meeting ID (PMI) Passcode: from Off to On",
"p_log_type": "Zoom.Operation",
}
- Name: Add User Group
ExpectedResult: false
Log:
{
"time": "2021-11-17 00:37:24Z",
"operator": "homer@panther.io",
"category_type": "User Group",
"action": "Add",
"operation_detail": "Add Group Engineers",
"p_log_type": "Zoom.Operation",
}
Detection logic
Condition
category_type eq "User Group"
This rule also runs imperative logic the parser cannot express as a filter; the conditions above are the structured part it could extract.
Indicators
Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.
| Field | Kind | Values |
|---|---|---|
category_type | eq |
|
Output fields
Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.
| Field |
|---|
operator |