Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Add support for threshold rules #63

Closed
threat-punter opened this issue Jul 15, 2020 · 2 comments · Fixed by #65
Closed

[FR] Add support for threshold rules #63

threat-punter opened this issue Jul 15, 2020 · 2 comments · Fixed by #65
Assignees
Labels
cli command line tooling enhancement New feature or request

Comments

@threat-punter
Copy link
Contributor

threat-punter commented Jul 15, 2020

Is your feature request related to a problem? Please describe.
N/A

Describe the solution you'd like
Our 7.9 release will provide support for threshold rules in the SIEM's detection engine. We need to add support to the detection-rules CLI for threshold rules.

Describe alternatives you've considered
N/A

Additional context
Below is an email threshold rule that I exported from the SIEM. Please note that including a value for field is not mandatory.

Example threshold rule
{
    "author": [],
    "actions": [],
    "created_at": "2020-07-15T03:55:01.873Z",
    "updated_at": "2020-07-15T13:23:49.678Z",
    "created_by": "threatpunter",
    "description": "Identifies a high number of failed Okta user authentication attempts from a single IP address, which could be indicative of a brute force or password spraying attack. An adversary may attempt a brute force or password spraying attack to obtain unauthorized access to user accounts.",
    "enabled": true,
    "false_positives": [],
    "filters": [],
    "from": "now-360s",
    "id": "a216c36f-1e60-49d7-b452-e6c0c0011929",
    "immutable": false,
    "index": [
        "filebeat-*"
    ],
    "interval": "5m",
    "rule_id": "db2efd83-4e17-4fd8-a56c-13c526722540",
    "language": "kuery",
    "license": "",
    "output_index": ".siem-signals-username-default",
    "max_signals": 100,
    "risk_score": 47,
    "risk_score_mapping": [],
    "name": "Okta Brute Force or Password Spraying Attack",
    "query": "event.module:okta and event.dataset:okta.system and event.category:authentication and event.outcome:failure",
    "references": [],
    "meta": {
        "from": "1m",
        "kibana_siem_app_url": "http://localhost:5603/jyr/app/security/detections"
    },
    "severity": "medium",
    "severity_mapping": [],
    "updated_by": "threatpunter",
    "tags": [
        "Elastic",
        "Okta"
    ],
    "to": "now",
    "type": "threshold",
    "threat": [],
    "threshold": {
        "field": "source.ip",
        "value": 25
    },
    "throttle": "no_actions",
    "version": 2,
    "exceptions_list": []
}
@threat-punter threat-punter added enhancement New feature or request cli command line tooling labels Jul 15, 2020
@brokensound77 brokensound77 changed the title [FR] Add support for threshold rules to detection-rules CLI [FR] Add support for threshold rules Jul 16, 2020
@brokensound77
Copy link
Contributor

brokensound77 commented Jul 16, 2020

Thanks for the info @threat-punter. I modified the title since there is more involved than the CLI, which should inherit support from the schema changes. I also reformatted the json data to be more readable.

REF: elastic/kibana#71371

@brokensound77 brokensound77 removed the cli command line tooling label Jul 16, 2020
@rw-access rw-access added the cli command line tooling label Jul 16, 2020
@brokensound77
Copy link
Contributor

resolved by #65

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cli command line tooling enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants