Traceability Loss - API Gateway
Description
Some AWS API Gateway instances do not enable the logging feature, discarding information that can be managed by other AWS services such as Cloudwatch to detect possible system anomalies
Impact
Lose traceability of events of interest to detect potential security breaches
Recommendation
- Enable the logging feature for all the API gateway instances
- Set a destination for the log files using other log services such as CloudWatch or Cloudtrail
Threat
Authenticated attacker from the Internet with access to the AWS console
Expected Remediation Time
⌚ 20 minutes.
Score
Default score using CVSS 3.1. It may change depending on the context of the src.
Base
- Attack vector: N
- Attack complexity: H
- Privileges required: H
- User interaction: N
- Scope: U
- Confidentiality: N
- Integrity: L
- Availability: N
Temporal
- Exploit code maturity: P
- Remediation level: O
- Report confidence: C
Result
- Vector string: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C
- Score:
- Severity:
Score 4.0
Default score using CVSS 4.0. It may change depending on the context of the src.
Base 4.0
- Attack vector: N
- Attack complexity: H
- Attack Requirements: N
- Privileges required: H
- User interaction: N
- Confidentiality (VC): N
- Integrity (VI): L
- Availability (VA): N
- Confidentiality (SC): N
- Integrity (SI): N
- Availability (SA): N
Threat 4.0
Result 4.0
- Vector string: CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
- Score:
- Severity:
Details
https://docs.bridgecrew.io/docs/logging_17
Requirements
Fixes
Free trial