prowler-cloud/prowler

[New Check]: SageMaker model monitoring schedules are active

Open

#11052 opened on May 6, 2026

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Python (8,957 stars) (1,322 forks)batch import
feature-requestgood first issuenew-checkprovider/aws

Description

Existing check search

  • I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist.

Provider

AWS

New provider name

No response

Service or product area

sagemaker

Suggested check name

sagemaker_models_monitor_enabled

Context and goal

  • Security condition to validate: At least one SageMaker monitoring schedule exists in the account/region and is in Scheduled status.
  • Why it matters: Model Monitor detects data drift, model quality issues, and bias drift in production. Without active monitoring, model degradation goes undetected and downstream decisions (fraud, access, pricing) silently degrade.
  • Resource involved: SageMaker monitoring schedule (MonitoringScheduleStatus, MonitoringType).

Expected behavior

  • Resource or scope to evaluate: SageMaker monitoring schedules in the account/region.
  • PASS when: at least one monitoring schedule exists and its status is Scheduled.
  • FAIL when: no monitoring schedule exists, or all existing schedules are in Pending, Failed, or Stopped status.

References

Suggested severity

Low

Additional implementation notes

No response

Contributor guide