forked from elastic/detection-rules
-
Notifications
You must be signed in to change notification settings - Fork 0
/
apm_405_response_method_not_allowed.toml
37 lines (34 loc) · 1.17 KB
/
apm_405_response_method_not_allowed.toml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
[metadata]
creation_date = "2020/02/18"
integration = ["apm"]
maturity = "production"
min_stack_comments = "New fields added: required_fields, related_integrations, setup"
min_stack_version = "8.3.0"
updated_date = "2022/12/14"
[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
'''