- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`Real-time monitoring of API calls can be achieved by directing CloudTrail logs to CloudWatch logs and establishing corresponding metric filters and alarms. It is recommended to set up a metric filter and alarm for console logins not protected by multi-factor authentication (MFA) to increase visibility into potentially at-risk accounts.
For instructions on setting up CloudWatch metric filters and alarms for logins without MFA, refer to the AWS CloudWatch Alarms for CloudTrail User Guide.
aws logs put-metric-filter \
--log-group-name <cloudtrail_log_group_name> \
--filter-name <no_mfa_console_signin_metric> \
--metric-transformations metricName=<no_mfa_console_signin_metric>,metricNamespace=CISBenchmark,metricValue=1 \
--filter-pattern '{ ($.eventName = "ConsoleLogin") && ($.additionalEventData.MFAUsed != "Yes") && \
($.userIdentity.type = "IAMUser") && ($.responseElements.ConsoleLogin = "Success") }'
aws cloudwatch put-metric-alarm \
--alarm-name <no_mfa_console_signin_alarm> \
--metric-name <no_mfa_console_signin_metric> \
--namespace "CISBenchmark" \
--statistic "Sum" \
--period 300 \
--threshold 1 \
--evaluation-periods 1 \
--comparison-operator GreaterThanOrEqualToThreshold \
--alarm-actions <sns_topic_arn>
You can choose your own metricName
and metricNamespace
strings. Use the same metricNamespace
for all Foundations Benchmark metrics to group them together.