Files
sigma-rules/rules/apm/apm_405_response_method_not_allowed.toml
T
Justin Ibarra 46d5e37b76 min_stack all rules to 8.3 (#2259)
* min_stack all rules to 8.3

* bump date

Co-authored-by: Mika Ayenson <mika.ayenson@elastic.co>
2022-08-24 10:38:49 -06:00

37 lines
1.2 KiB
TOML

[metadata]
creation_date = "2020/02/18"
maturity = "production"
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
min_stack_version = "8.3.0"
updated_date = "2022/08/24"
[rule]
author = ["Elastic"]
description = """
A request to a web application returned a 405 response, which indicates the web application declined to process the
request because the HTTP method is not allowed for the resource.
"""
false_positives = [
"""
Security scans and tests may result in these errors. Misconfigured or buggy applications may produce large numbers
of these errors. If the source is unexpected, the user unauthorized, or the request unusual, these may indicate
suspicious or malicious activity.
""",
]
index = ["apm-*-transaction*", "traces-apm*"]
language = "kuery"
license = "Elastic License v2"
name = "Web Application Suspicious Activity: Unauthorized Method"
references = ["https://en.wikipedia.org/wiki/HTTP_405"]
risk_score = 47
rule_id = "75ee75d8-c180-481c-ba88-ee50129a6aef"
severity = "medium"
tags = ["Elastic", "APM"]
timestamp_override = "event.ingested"
type = "query"
query = '''
http.response.status_code:405
'''