detection.wiki

Detection rules › Panther

A Login from Outside the Corporate Office

Severity
high
Log types
Osquery.Differential
Tags
Configuration Required, Osquery, Linux, Initial Access:Valid Accounts
Reference
https://attack.mitre.org/techniques/T1078/
Source
github.com/panther-labs/panther-analysis

A system has been logged into from a non approved IP space.

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1078 Valid Accounts

Rule body yaml

AnalysisType: rule
Filename: osquery_linux_logins_non_office.py
RuleID: "Osquery.Linux.LoginFromNonOffice"
DisplayName: "A Login from Outside the Corporate Office"
Enabled: false
LogTypes:
  - Osquery.Differential
Tags:
  - Configuration Required
  - Osquery
  - Linux
  - Initial Access:Valid Accounts
Reports:
  MITRE ATT&CK:
    - TA0001:T1078
Severity: High
Description: A system has been logged into from a non approved IP space.
Runbook: Analyze the host IP, and if possible, update allowlist or fix ACL.
Reference: https://attack.mitre.org/techniques/T1078/
SummaryAttributes:
  - name
  - action
  - p_any_ip_addresses
  - p_any_domain_names
Tests:
  - Name: Non-office network login (logged_in_users)
    ExpectedResult: true
    Log:
      {
        "name": "pack/incident_response/logged_in_users",
        "action": "added",
        "columns": { "host": "10.0.3.1", "type": "user", "user": "ubuntu" },
      }
  - Name: Non-office network login (last)
    ExpectedResult: true
    Log:
      {
        "name": "pack-incident_response-last",
        "action": "added",
        "columns":
          {
            "host": "10.0.3.1",
            "type": "8",
            "username": "ubuntu",
            "tty": "ttys008",
            "pid": "648",
            "time": "1587502574",
          },
      }
  - Name: Office network login
    ExpectedResult: false
    Log:
      {
        "name": "pack-logged_in_users",
        "action": "added",
        "columns": { "host": "192.168.1.200", "user": "ubuntu" },
      }

Detection logic

Condition

action eq "added"

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.

FieldKindValues
actioneq
  • added corpus 10 (panther 10)

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.

FieldSource
usercolumns.user