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 madurity: 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:
  • Base: 2.2
  • Temporal: 2.0
• Severity:
  • Base: Low
  • Temporal: Low

Details

https://docs.bridgecrew.io/docs/logging_17

Requirements

• 075.Record exceptional events in logs
• 079.Record exact occurrence time of events
• 376.Register severity level

Fixes

• Aws

free trial

Search for vulnerabilities in your apps for free with our automated security testing! Start your 21-day free trial and discover the benefits of our Continuous Hacking Machine Plan. If you prefer a full service that includes the expertise of our ethical hackers, don't hesitate to contact us for our Continuous Hacking Squad Plan.